> For the complete documentation index, see [llms.txt](https://help.brieftech.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.brieftech.ai/reference/background-jobs.md).

# Background Jobs

The Background Jobs dialog lists the server-side jobs queued from your matter in the last 48 hours — for example, batch OCR, fact extraction, Document Index export, and court bundle creation. Quick jobs that finish on the spot are listed too, so a row may go straight to **success** with a very short duration.

Open it from the top bar, while you have a matter open:

* Click the <img src="/files/Kb8zyAIYK1cMKC4IbdtS" alt="background jobs" data-size="line"> icon to open the dialog. The icon appears only inside a matter.
* The icon pulses while one or more jobs are running or still queued (pending).
* Hovering it shows a live count of those jobs — for example "3 jobs running..." — or "View background jobs" when none are active.

## Columns

| Column   | Meaning                                                                                                                                                                                          |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Function | The internal name of the job — for example `ocrGcsBatch`, `extractFilesBatch`, `extractFacts`, `exportLod`, `generateCharacterSummary`, `readDocuments`, or `agent.bundleCreation.createBundle`. |
| Status   | Current job status. See **Status badges** below.                                                                                                                                                 |
| Created  | Local timestamp when the job was queued.                                                                                                                                                         |
| Duration | Elapsed time between the job starting and ending. Shows a dash ("-") until the job has finished — including while it is still queued or running.                                                 |

The table is sorted by **Created** (newest first) and starts at ten rows per page; you can sort by any column heading and change the page size. The list updates by itself as jobs progress. A matter with no jobs in the last 48 hours shows "No data available".

## Status badges

| Status    | Colour | Meaning                                             |
| --------- | ------ | --------------------------------------------------- |
| pending   | Grey   | The job is queued but has not started on Cloud Run. |
| starting  | Grey   | Cloud Run is provisioning the job.                  |
| running   | Blue   | The job is executing.                               |
| success   | Green  | The job finished successfully.                      |
| error     | Red    | The job failed.                                     |
| cancelled | Grey   | The job was cancelled before it finished.           |

## Row actions

Clicking a row opens the [Job Logs](/reference/job-logs.md) dialog for that job, where you can follow its progress.

Two more buttons sit in the **Status** column, to the right of the status badge. Both are BriefTech support tools: they appear for everyone, but only BriefTech support can use them.

| Button                   | What it does                                                                                                                                                                                                                                                                                                                                           |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Refresh (circular arrow) | Re-reads the job's status from Cloud Run and writes it back. It only asks Cloud Run for the job's live status when the job has a server execution name recorded against it; for a job without one it writes back the status already stored, so the displayed row cannot change. Refresh reports success either way — it does not check what came back. |
| Error (red exclamation)  | Shown only for **pending** jobs. Marks the job as `error` after confirmation. This changes the row's status so the job stops showing as pending; it does not stop work that has already started, and it does not fill in the Duration column.                                                                                                          |

Clicking either button acts on that button only — it does not also open the Job Logs dialog.

If a job is stuck, contact BriefTech support.

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Document processing and errors</strong></td><td>Processing stages, OCR page limits, and the document error reasons.</td><td><a href="/pages/tPz7A2YvClfBc391MwH2">/pages/tPz7A2YvClfBc391MwH2</a></td></tr><tr><td><strong>Upload monitor</strong></td><td>Status indicators, filter tabs, and actions in the upload monitor panel.</td><td><a href="/pages/eMSF982FPxH21UGFZ0Vb">/pages/eMSF982FPxH21UGFZ0Vb</a></td></tr><tr><td><strong>The document lifecycle: from upload to ready</strong></td><td>What happens to a file between upload and the moment it can be used.</td><td><a href="/pages/u8eIgAY8I81LcXEFoaCo">/pages/u8eIgAY8I81LcXEFoaCo</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.brieftech.ai/reference/background-jobs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.