tiennm99/openai-status-bot
1
0 Fork 0
mirror of https://github.com/tiennm99/openai-status-bot.git synced 2026-10-20 00:15:34 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(mongo): restore redis parity safeguards

Browse Source
This commit is contained in:
tiennm99 committed 2026-06-27 16:05:32 +07:00
1 parent 7c6de7ac6d
commit ea1005c2e8
8 files changed
+377 -39
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

README.md
+1 -1
View File
@@ -79,7 +79,7 @@ The bot always reads OpenAI status from `https://status.openai.com`.
The first successful poll seeds the database and does not send historical incidents. Notifications start from later changes.
Switching from a prior Redis deployment starts from empty state: there is no data migration, so subscribers must re-issue `/start` and component checkpoints reseed on the first poll.
Switching from a prior Redis deployment starts from empty state: there is no data migration, so subscribers must re-issue `/start`, component checkpoints reseed on the first poll, and the stored Telegram update offset is not migrated, so retained Telegram updates can be reprocessed once after cutover.
Incident update dedupe tracks the update content/version, so edited Statuspage updates can notify again. Each event is checkpointed independently once it has fully fanned out, so a retryable Telegram failure on one event only defers that event for retry on a later poll and never blocks checkpoints for other events delivered in the same poll.