PREPROD
ReaderAuthor

suite

Replay Jobs

Operator-initiated jobs that re-deliver historical events from the native stream to clearinghouse consumers.

1 min read · 2 depth levelsstratum-suite · vdevMatches production
Everyday

Replay Jobs, at /admin/catalog/replay, let a super-admin re-send events after a fix or a newly added subscription. Each job replays every event in a date range (rangeFrom to rangeTo) for a single required tenantId, optionally narrowed to one consumerProduct (all products if blank). The list shows each job's Status, Tenant ID, Range, Consumer, a Progress bar built from eventsProcessed over eventsTotal, and its Pinning. A job moves through the statuses queued, running, cancelling, done, failed, and cancelled; live jobs auto-refresh every 10 seconds and can be cancelled at the next batch boundary. Pinning (the snapshotResolution) controls which registry snapshot the replay uses — live, freeze, atTime, or explicit. The detail page reports Events processed / total, a Processed %, start and finish times, and a Last error card when a job fails. Creating a job that overlaps an existing range is rejected with a link to the conflicting job.

Technical section
Data model, API, and internals — visible to developers.
View as developer
Was this helpful?