Durable processes and notifications
Accept long-running work immediately and make every stage understandable.
On this page
Canonical source
This public guide is distilled from docs/PROCESS-SYSTEM.md and docs/PROCESS-ROLLOUT.md. Keep implementation detail in those repository documents.
A user-facing control plane
PostgreSQL owns process truth, Electric delivers authorized changes, and BullMQ owns execution, retries, schedules, and external effects. Queued, running, waiting, succeeded, failed, and canceled are explicit states rather than inferred spinner behavior.
- Accepted work returns a committed queued snapshot immediately.
- Milestones explain meaningful stages without storing provider payloads.
- Terminal notifications are recipient-scoped and deduplicated.
- Recovery commands are capability-gated, idempotent, and auditable.
Roll out with evidence
Database query-plan certification, authenticated preview journeys, canary evidence, and forward-only recovery are different gates. A local process test never becomes a claim about live Electric convergence or provider health.
Follow an automation through its run
Open an automation to configure its workflow and inspect its run history. Each run links to Background work for progress and milestones; the process detail links back to the automation and identifies the definition version that ran. Inbox notifications lead to the corresponding process when a destination is available.
Was this page helpful?
Feedback is stored only in this browser in the starter implementation.