Administration
Inspect and retry background jobs
Read bounded job queues, retry eligible work, and inspect source records or EHR payloads.
Global administrators inspect Admin → Dashboard → Jobs for recent work and eligible recovery actions. Organization roles alone do not grant access.
Inspect a job
- Open Failed Jobs or Recent Jobs.
- Find the subject and work kind.
- Read Status, Reason, Attempts, and Updated.
- Open the offered Report, Guide, Form, or Person link when you need the source record.
- Use Audit for recorded events.
Source links still require access to their destinations. Audit opens the general audit view; it does not automatically filter history to that job.
Understand the queue limits
Both cards use the 40 most recently updated jobs returned to this dashboard. Failed Jobs displays at most eight entries, prioritizing retryable work, then failed/blocked work and recent updates.
Recent Jobs displays only the first ten entries. Its total badge can be larger than the displayed list. Neither card has a Load more control here. An empty card does not prove that no older failed jobs exist.
Job kinds include media, reminders, Report/EHR exports, Guide/Form package imports and exports, native uploads, and document extraction. Not every kind supports Retry.
Retry eligible work
- Read the failure and address its cause.
- Select Retry when enabled.
- Wait while that row shows Retrying.
- Inspect its returned state and attempts.
- Follow live updates, or use Dashboard → Overview → Refresh.
- Check the source result after processing finishes.
Retry acts immediately without a confirmation. Eligibility is checked again when requested, so a stale button can be rejected.
Missing source records or packages, unavailable destinations, exhausted attempts, unsupported work, or unsafe partial imports can block retry. A partially created Guide/Form import can require cleanup or review before replay. This screen does not perform that repair on demand.
Reminders stay with their reminder worker. Document extraction is recovered through its source document workflow; these rows do not offer an enabled administrative Retry.
An accepted retry does not prove completion. If the action or subsequent refresh fails, read the current state before requesting it again.
Live updates and downloads
Live stream active, Live stream degraded, Polling fallback, or Live status pending describe how the job view receives updates, not whether a particular job succeeded. Expand Technical details only when needed for diagnosis.
A successful EHR-export row can enable Payload. Select it to save the stored JSON payload through your device's download, save, or sharing flow. The payload can still be unavailable; a successful job badge does not verify the download. It can contain care data, so use an authorized destination.
The Native Uploads guide explains mobile evidence recovery and why requeuing is different from completing an upload.