SEOAI
Sign in

Runs and the queue

How scheduled and manual runs are processed, and how to read the queue page.

Every run, scheduled or manual, produces executions that a background worker processes as capacity allows. You do not need to keep the app open: the scheduler checks topic schedules continuously and enqueues runs that are due.

The queue page

The Queue page shows live activity and refreshes every 15 seconds.

The four stat cards at the top:

  1. Pending: executions waiting to run
  2. Processing: executions currently claimed by a worker
  3. Completed in the last hour
  4. Failed in the last hour
If Pending keeps climbing and nothing completes, the worker may be down. Failed executions show the exact error, and repeated provider failures can be surfaced by email through the scan-failure notification setting.

Statuses

  1. Queued: waiting to run
  2. Running: claimed by a worker
  3. Done: finished, result available
  4. Failed: something went wrong
  5. Skipped: not executed, for example due to AI Overview backoff or a missing credential

Common errors and what they mean

  1. Invalid API key: the stored credential was rejected, re-save it in API Settings
  2. Provider rate limit or timeout: the AI platform throttled or stalled; jobs retry
  3. Plan quota exhausted: platform executions are used up for this month
  4. API key out of quota or credit: your own provider key needs topping up
  5. No API key configured: add the credential for that platform
  6. Cancelled: the job was cancelled from the queue

You can cancel queued jobs, and every done job links straight to its result view.

Your first tracking run

Scan failures

Notification preferences