Monitor jobs
Find and follow your submissions on the Jobs screen — read a job's status, filter the list to the runs you care about, and open a job to see its documents and outcome.
Every submission to a pipeline — from the app, the API, the Playground, or a connector — becomes a job. The Jobs screen is where you watch those jobs move from submitted to finished, see how each one turned out, and open the ones that need a closer look.
Anyone tracking what the platform is processing — operators watching a queue and developers confirming an integration's submissions landed. Reading Jobs needs no special permission beyond access to the workspace.
Prefer to see it first? This walkthrough tours the Jobs screen and the details behind a single job.
A click-through of the Jobs screen — reading the list, opening a job, and following it through to its documents and outcome. It runs in your browser and loads nothing until you press play.
1. Open Jobs
Open Jobs from the navigation. The screen lists submissions newest-first, each row a single job with its pipeline, status, and when it was submitted.
The Jobs screen. A Production / Test split sits above the list; the row that is still running shows the stage it is on, and the filter bar below narrows the list by status, time, pipeline, or submitter.
2. Read a job's status
A job carries one status as it runs. The states mirror what a run can end in anywhere on the platform:
- Processing — accepted and moving through the pipeline's stages.
- Completed — finished cleanly, with data ready to read or deliver.
- Needs review / Awaiting review — one or more documents raised an exception and are waiting in the Reviews workspace.
- Failed / Blocked — the run stopped before finishing, or was blocked (for example, on credits).
Processing is asynchronous, so a freshly submitted job shows as processing and updates in place as it completes — you do not need to resubmit to refresh it.
3. Filter and find a job
Narrow the list to the jobs you care about — by status, by pipeline, or by the source_tag stamped on the submission. Tagging your submissions (see Submit a job) is what makes a batch findable here later, so set a tag you will recognise when you submit.
4. Open a job
Select a row to open the job. A job can contain more than one document — a multi-page upload is split into the documents it actually holds — so the job view lists each document with its own status alongside the job's overall outcome. From here you can open a document to read its extracted data (see Review extracted documents).
5. Act on the outcome
What to do next follows the status:
- Completed — read the documents, or let the pipeline's destination deliver them.
- Needs review — work the exceptions in Reviews; see Correct a document in review.
- Failed / Blocked — check the reason on the job, fix the cause, and resubmit.
To follow jobs without watching this screen, subscribe to job events with a webhook — see Subscribe to job events.