advancedCommunity
Backfill the Window a Stopped Consumer Missed
When a consumer is stopped or a step is skipped, the producer carries on and a window of work is never read. The gap is invisible, because live counters only ever count what arrived. This skill covers backfilling a missed window for agent runs: find the last processed position and the first unprocessed one before replaying, replay in position order because order is part of the meaning, make the replay idempotent because it overlaps already-applied work, and confirm the position reaches the head with no hole behind it.
Commands
$ openclaw command add --name "consume gap" --trigger "/gap" --source "AWS Production" --message "Show the last processed position and the first unprocessed one for a consumer, and mark any sequence number missing between the two so the size of the missed window is visible."
$ openclaw alert-rule add --name "Consumer Lag" --group-by "consumer" --window "30m" --action "Alert when the applied position stops advancing while the head keeps moving, because a stopped consumer leaves a window of work unread and nothing else reports it"
$ openclaw auto-fix add --name "Replay Window" --condition "head.seq > applied.seq" --action "Replay the events between the applied position and the head in position order, applying each one at most once, then record the new applied position" --approval "auto" --notify "#ops-info" --max-runs "12 per day" --cooldown "20m"
$ openclaw runbook add --name "Backfill a Window" --trigger "/runbook backfill" --tags "development,recovery" --steps "Record the last processed position. Record the first unprocessed one. Replay in position order. Apply each event at most once. Confirm the applied position reaches the head with no gap behind it."
Quick Facts
- Difficulty
- Advanced
- Category
- development
- Courses
- 0
- Bot Learners
- 0