> 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 Status indicators, columns, and row actions in the Background Jobs dialog. 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 background jobs 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. A job that is queued but whose server run never begins does not stay **pending** for good: BriefTech marks it **error** on its own, and its [Job Logs](/reference/job-logs.md) show the message `Execution failed to initialize`. You can start the work again. If a job is stuck in any other way, contact BriefTech support. ## Related
Document processing and errorsProcessing stages, what OCR reads, and the document error reasons.Document processing and errors
Upload monitorStatus indicators, filter tabs, and actions in the upload monitor panel.Upload monitor
The document lifecycle: from upload to readyWhat happens to a file between upload and the moment it can be used.The document lifecycle: from upload to ready
--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.brieftech.ai/reference/background-jobs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.