Read the Queue and Workers pages
Queue shows the background jobs the platform has really run, with status, failures in a row, last duration and the email outbox backlog. Workers lists each known background task and who triggers it: this platform has no persistent worker process.
Have questions or need step-by-step guidance on this topic?
Step-by-Step Procedure
Open Queue
Open "System Operations" and click "Queue" (address /admin/system/queue). Tiles: "Jobs recorded", "Running now", "Failing (not yet dead)", "Dead-lettered" and "Email outbox waiting".
Read the table
Each row is one job with "Status", "Triggered by", "Retryable", "Failures in a row", "Recorded runs", "Last run", "Last duration (ms)", "Next run" and "Last error". A job appears only after its first real run.
Open Workers
Click "Workers" (address /admin/system/workers). The tile "Persistent worker processes" is 0 by design; each row is a known task with its trigger, endpoint, whether it is safe to retry and its last run ("NEVER_RUN" when it has not run).
Know what is recorded
Price refresh, email outbox flush, the stale-meeting reaper (real runs only, not previews) and the retention purge are recorded. If the page says the job ledger is not applied, ask the platform owner to run "npm run db:apply:system-ops"; until then nothing can be recorded and the page has no data.
You know which background tasks exist, which ran, which are failing and whether the email outbox has a backlog.
Troubleshooting & Failure Modes
Was this guide helpful?
Help us refine our platform documentation