Skip to content

Commit

Permalink
Revert "Expose transaction ID in GET response"
Browse files Browse the repository at this point in the history
This reverts commit 772590f.
Clients should keep track of transaction IDs themselves.
  • Loading branch information
AndrewFerr committed Sep 11, 2024
1 parent 8523ed4 commit 883e6b5
Showing 1 changed file with 0 additions and 2 deletions.
2 changes: 0 additions & 2 deletions proposals/4140-delayed-events-futures.md
Original file line number Diff line number Diff line change
Expand Up @@ -199,7 +199,6 @@ The response is a JSON object containing the following fields:
- `room_id` - Required. The room ID of the delayed event.
- `type` - Required. The event type of the delayed event.
- `state_key` - Optional. The state key of the delayed event if it is a state event.
- `transaction_id` - Optional. The transaction ID of the delayed event if it is a regular (non-state) event.
- `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.
Expand All @@ -221,7 +220,6 @@ Content-Type: application/json
"type": "m.room.message",
"delay": 15000,
"running_since": 1721732853284,
"transaction_id": "abcdefgh",
"content":{
"msgtype": "m.text",
"body": "I am now offline"
Expand Down

0 comments on commit 883e6b5

Please sign in to comment.