> 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/job-logs.md). # Job Logs The Job Logs dialog shows what a single background job is doing: how far along it is, what it has recorded, and — while it is still running — a button to cancel it. ## Opening it Click any row in the [Background Jobs](/reference/background-jobs.md) dialog to open the logs for that job. Some screens also offer a button to open it directly for a job they started. It also opens by itself when you start work that runs as a background job: creating a court bundle, running batch OCR, and extracting embedded files or email attachments when the job is large enough to be offloaded. You can close it and carry on working; the job keeps running. ## When a job runs in the cloud A court bundle is offloaded to the cloud when the documents in the collection you are bundling total about 1,000 pages or more — counted across every document in that collection that you have not moved to the Bin, not just the volumes you are assembling. Smaller runs finish in place. Where the completion message reaches you follows from that. A run that finishes in place tells you wherever you are in the app. An offloaded run reaches you with its message only if you are on the Index tab tab when it lands — though if you come back before it finishes, BriefTech picks the job up again and you still get it. ## What it shows A line at the top identifies the job with four values: the account the matter belongs to, the matter's ID, the job ID, and the server execution name. The first value is the matter's owner, who may not be you — on a matter shared with you it appears as the owner's internal user ID rather than an email address. Below it: | Field | Meaning | | -------- | --------------------------------------------------------------------------------------------------------------------------------------- | | Status | The job's current status, shown as a chip in capitals. See [Background Jobs](/reference/background-jobs.md) for what each status means. | | Function | The internal name of the job. | | Created | When the job was queued. | | Started | When the job began running. Shows a dash ("-") until then. | | Ended | When the job finished. Shows a dash ("-") until then. | | Error | The error message, shown only when the job has failed. | ## Cancelling a job The **Cancel job** button appears while the job has a server execution name recorded — the fourth value in the line at the top — and has not yet finished. It is not there before the job starts, because the execution name is only recorded when the job begins running; and a job that runs without one recorded shows no button either. For a court bundle that means the button appears only on a run that was offloaded to the cloud, and only once that run has started — while the job is still being provisioned, in the **Preparing** stage, there is nothing to click yet. The button goes once the job has finished. Cancelling does not always remove it straight away: the app re-checks the execution after sending the cancellation, and if the server does not yet show it as finished, the job is re-recorded at the stage that check found it — pending, starting, or running — and the button stays. Cancelling requires editor or owner access to the matter. It shows a "Cancellation requested" message and records the request in the log. ## While the job is starting A job whose status is **pending** shows a **Preparing** section: a spinner, a message that changes as time passes, an animated orange bar, and an elapsed-time counter. On-screen guidance notes that large requests take 30–60s to start. A strip below it lists the start-up stages — Queued, Provisioning, Warming up, Running, Packaging, Done. Only the first three ever light up; the last three are placeholders that stay grey. The section is replaced by the progress bar once the job leaves **pending**. ## Progress A progress bar shows how far the job has got, with the percentage in the middle. The bar turns red if the job fails. The short message below the bar is generic — it is chosen from the percentage alone, so it may not describe what your particular job is doing. A job whose work does not report progress stays at 0% for the whole run, including after it has finished. ## Log Details **Log Details** is collapsed by default — expand it to see the individual log entries, oldest first. The list scrolls to the newest entry as the job runs; scroll up and it stops following, and scrolling back to the bottom starts it again. Each entry has a level, a timestamp and a message. Levels are shown in capitals: | Level | Colour | | ----- | ------ | | DEBUG | Grey | | INFO | Blue | | WARN | Amber | | ERROR | Red | Where an entry carries extra detail, an information icon appears beside it — hover it to see the detail. A job with no log entries yet shows "No logs available". ## Related
Background JobsStatus indicators, columns, and row actions in the Background Jobs dialog./pages/REaGxjKXuLlDxbm28MDE
Document processing and errorsProcessing stages, OCR page limits, and the document error reasons./pages/tPz7A2YvClfBc391MwH2
The document lifecycle: from upload to readyWhat happens to a file between upload and the moment it can be used./pages/u8eIgAY8I81LcXEFoaCo
--- # 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/job-logs.md?ask=&goal= ``` `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.