Review native upload recovery

Global administrators use Admin → Dashboard → Jobs → Native Uploads to inspect session-evidence jobs waiting for packaged mobile upload completion.

Read the summary

1. Open the Native Uploads card.
2. Compare Stalled, Active, Retryable, Done, and Total.
3. Open Failed Jobs or Recent Jobs for an individual job.
4. Read its failure, attempts, update time, and available source link.
5. Check the relevant session or Report evidence when investigating completion.

The summary counts native-upload jobs within the dashboard's returned 40-job window, shared with other work types. It is not an inventory of all uploads on every device.

Stalled counts failed or blocked jobs. Active includes queued, pending, uploading, processing, retrying, and running work. Done includes completed, ready, succeeded, or delivered states. A retrying job can be both Active and Retryable, so these counts are not mutually exclusive.

The summary itself has no per-job action or full-history link. Failed Jobs shows at most eight selected entries and Recent Jobs shows ten; a counted native job may not appear in either visible subset.

Requeue a stalled upload

1. Locate the job in Failed Jobs or Recent Jobs.
2. Resolve its visible failure when possible.
3. Select Retry if enabled.
4. Check that the returned state changes to queued or otherwise progresses.
5. Follow the source device's upload and confirm the evidence becomes available.

Requeue is available for eligible failed, blocked, or retrying native jobs that retain a source session and have attempts remaining. Completed work, work still uploading, non-retryable failures, missing sessions, or exhausted attempts cannot be requeued through this action.

The request requeues the existing job and records an audit event. It does not reset its recorded attempt count, upload the file itself, or recreate missing device evidence. The mobile upload process still has to complete.

Recover when progress stops

Return the source device to a usable connection and the supported app, then inspect its upload state. Browser administration cannot supply a file that only existed on another device.

If Retry is unavailable or the job repeatedly fails, record the subject, failure, attempts, updated time, and relevant source. Use an authorized support channel. Avoid repeatedly creating replacement uploads until you understand which evidence is missing.

An empty Native Uploads card means no native jobs are present in this returned window; it does not prove the device has no pending transfer.