Correctly-cased immediate acknowledgement delivery

setting pendingEvent status to encrypting in !AbCdEf1234567890:example.org event ID ~!AbCdEf1234567890:example.org:m<redacted>.1 -> undefined setting pendingEvent status to sending in !AbCdEf1234567890:example.org event ID ~!AbCdEf1234567890:example.org:m<redacted>.1 -> undefined setting pendingEvent status to sent in !AbCdEf1234567890:example.org event ID $<redacted> -> $<redacted>

Created cron job stores lowercased Matrix room ID

{ "id": "<redacted>", "agentId": "alpha", "sessionKey": "agent:alpha:matrix:channel:!abcdef1234567890:example.org", "sessionTarget": "session:agent:alpha:matrix:channel:!abcdef1234567890:example.org", "payload": { "kind": "agentTurn", "message": "Reminder message", "timeoutSeconds": 60 }, "delivery": { "mode": "announce", "to": "!abcdef1234567890:example.org", "channel": "matrix" } }

Cron run generated the final text but delivery failed

{ "action": "finished", "status": "error", "error": "M_UNKNOWN: MatrixError: [500] non-create event for room of unknown version in !abcdef1234567890:example.org", "summary": "Ping - one minute's up.", "delivery": { "intended": { "channel": "matrix", "to": "!abcdef1234567890:example.org", "source": "explicit" }, "resolved": { "ok": true, "channel": "matrix", "to": "!abcdef1234567890:example.org", "accountId": "default", "source": "explicit" }, "fallbackUsed": true, "delivered": false } }

Queue 'message' giving up on event ~!abcdef1234567890:example.org:m<redacted>.2

TL;DR

The issue can be fixed by preserving the original casing of the Matrix room ID when creating a scheduled job for cron announce delivery.

Guidance

• Verify that the Matrix room ID is being lowercased when creating the cron job by checking the sessionKey and delivery.to fields in the job data.
• Update the code to preserve the original casing of the Matrix room ID when creating the cron job, ensuring that sessionKey and delivery.to fields match the original room ID casing.
• Test the fix by running the same steps to reproduce the issue and verifying that the scheduled message is delivered to the correct room.
• Consider updating the related issues (#57321, #63828, #25318) to ensure that the fix is applied consistently across the codebase.

Example

No code snippet is provided as the issue does not include specific code details, but the fix would involve updating the cron job creation logic to preserve the original casing of the Matrix room ID.

Notes

The issue is specific to Matrix rooms with mixed-case IDs and cron announce delivery, so the fix should be targeted to this specific use case.

Recommendation

Apply a workaround to preserve the original casing of the Matrix room ID when creating cron jobs for announce delivery, as this is a high-severity issue that affects scheduled reminders and cron announcements.