Find the state that needs attention
| State | What to do |
|---|---|
| Queued | The background worker has not started the work yet. Retain the job reference and check its next status update. |
| Running | Read the current stage and per-site progress. Large inventories and provider throttling can take time. |
| Waiting for approval | Open Review and approve. Resolve outstanding decisions; execution is not expected to begin yet. |
| Checking source / waiting for a safety decision | Open the source safety-check panel and inspect changes or the pending decision. |
| Failed / stopped | Read the failed stage and error. Follow the failure-recovery guide rather than treating it as an active run. |
Use these checks in order
- Make sure you are viewing the intended project, batch, and run, especially after opening another browser tab.
- Use the relevant refresh control or reopen the same batch.
- Check connection status if the error indicates authorization or resource access.
- Look for a source-change or identity-review decision that is waiting for you.
- If the same state persists without progress or a useful error, send support the run reference, last progress text, and approximate start time.
Keep the original work traceable
Avoid creating several replacement batches for the same scope while the original job may still be running. Multiple run IDs make it harder to understand which attempt made a change or owns a credit reservation.
Reserved credits can remain while an interrupted job is investigated. Treat a persistent reservation as part of the incomplete run and include it in the support request; do not assume it is a second successful charge.