Job status reference
What each run status means — Success, Partial Success, Failure, No Files, and Skipped — and what to do about it.
Last updated July 17, 2026
#Status meanings
| Status | Meaning | What to do |
|---|---|---|
| Success | The run completed and all selected files were processed. | Nothing — this is the goal. |
| Partial Success | The run completed but some files weren't processed — individual files failed or were skipped. | Open the run detail to see which files, and why. |
| Failure | The run could not complete. | Read the error in the run detail; it names the connection, permission, or path problem. |
| No Files | The run executed normally but found nothing to process. | Normal for jobs that only sometimes have work; investigate if this job should have had files. |
| Skipped | The run didn't execute this time — for example, because a previous run of the same job was still in progress. | Check whether runs are overlapping; consider a longer interval or shorter job. |
#How statuses are used
Statuses roll up to the Dashboard and drive alerts. A “No Files” result is normal for jobs that only sometimes have work — but a job that should have files and reports zero is worth a look.