From eb0a50487b8ad4929ec67ca1f2c397c4e2ddee18 Mon Sep 17 00:00:00 2001 From: Andrew Ferrazzutti Date: Fri, 10 Oct 2025 01:53:23 -0400 Subject: [PATCH] Always require origin_server_ts on finalised evts It is either the send time, or the cancel/error time --- proposals/4140-delayed-events-futures.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/4140-delayed-events-futures.md b/proposals/4140-delayed-events-futures.md index dc7b9c23a..da2ac931e 100644 --- a/proposals/4140-delayed-events-futures.md +++ b/proposals/4140-delayed-events-futures.md @@ -202,7 +202,7 @@ These objects contain the following fields: - `error` - Optional. A Matrix error (as defined by [Standard error response](https://spec.matrix.org/v1.16/client-server-api/#standard-error-response)) to explain why this event failed to be sent. - `event_id` - Optional. The `event_id` this event got in case it was sent. - - `origin_server_ts` - Optional. The timestamp of when the event was sent. + - `origin_server_ts` - Required. The timestamp of when the event was finalised. - `next_batch` - Optional. A token that can be used to paginate the list of delayed events. The batch size and the amount of terminated events that stay on the homeserver can be chosen, by the homeserver.