This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Keep track when we try to backfill an event #13621
Labels
A-Messages-Endpoint
/messages client API endpoint (`RoomMessageListRestServlet`) (which also triggers /backfill)
A-Performance
Performance, both client-facing and admin-facing
O-Uncommon
Most users are unlikely to come across this or unexpected workflow
S-Minor
Blocks non-critical functionality, workarounds exist.
T-Task
Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.
Milestone
Mentioned in internal doc about speeding up
/messages
. Related to #13356Keep track when we try to backfill an event. In other words, when an event fails to backfill, we can record it in the database.
This is a building block so we can later:
/messages
slow when we know it will probably fail again -> Process previously failed backfill events in the background #13623The text was updated successfully, but these errors were encountered: