From 114da1e31e753722a7a0643b478b9f63dbdd5389 Mon Sep 17 00:00:00 2001 From: Hugh Nimmo-Smith Date: Thu, 25 Jul 2024 18:33:40 +0100 Subject: [PATCH] Clarify contents of content field on GET response --- proposals/4140-delayed-events-futures.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/proposals/4140-delayed-events-futures.md b/proposals/4140-delayed-events-futures.md index b8f583086..02a6a760c 100644 --- a/proposals/4140-delayed-events-futures.md +++ b/proposals/4140-delayed-events-futures.md @@ -199,7 +199,8 @@ The response is a JSON object containing the following fields: - `delay` - Required. The delay in milliseconds before the event is sent. - `running_since` - Required. The timestamp (as unix time in milliseconds) when the delayed event was scheduled or last restarted. - - `content` - Required. The content of the delayed event. + - `content` - Required. The content of the delayed event. This is the body of the original `PUT` request not a preview + of the full event after sending. - `next_batch` - Optional. A token that can be used to paginate the list of delayed events. For example: