> For the complete documentation index, see [llms.txt](https://docs.cw.crisisworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cw.crisisworks.com/concepts-and-fundamentals/on-a-computer/your-user-profile-and-duties/background-processes.md).

# Background Processes

## Overview

The system is comprised of a number of queues that run continuously and provide parallelised task processing.

The system has a powerful command runner to allow administrators to track and manage all background tasks

The Background Processes console shows the status of each of the configured queues, along with the status of each Scheduled Jobs.

### Access

Diagnostics is accessed from the [User Menu](/concepts-and-fundamentals/on-a-computer/your-user-profile-and-duties.md#user-menu) via the Background Processes link under SYSTEM.

<figure><img src="/files/CY18lLgKMQecjK76TEiA" alt="" width="224"><figcaption><p>Background Processes link in the User Menu</p></figcaption></figure>

## Using the Processes List

The Background Processes screen lists the most recently run processes by the date of creation.

Each process has a unique ID, a Name (based on the process you've run), Queue, Date Created and Status.

<figure><img src="/files/rvnUPWSQM5QOLYH3Bo3V" alt=""><figcaption><p>Background Processes list</p></figcaption></figure>

### Queues

Queues are sorted into schedulers run based on the type of process you're running or the configuration of your site (certain processes are allocated higher priority/processing power). Each process has different timeframes and limits. These are listed for technical reference only. If your process consistently fails, it may be useful for Datalink support to identify which queue the process ran on.

<table><thead><tr><th width="158.85546875">Queue name</th><th>Process type / Module or Register</th></tr></thead><tbody><tr><td>report</td><td><a href="/pages/A0dE4zj63zrbxX5ddKH2">Report</a></td></tr><tr><td>messaging</td><td><a href="/pages/96Wl4ZyuvvALoh43jcys">Communications</a> </td></tr><tr><td>import</td><td><a href="/pages/QP6MVwI3qEAEvatbmPc3">Import</a> </td></tr><tr><td>lambda, fargate</td><td>AWS computing services used for other processes, such as <a href="/pages/85HyYT6h2YqK6Qk26AXL#generate-merge">Generate Merge</a></td></tr></tbody></table>

### Status

The Status tells you the current stage of the process.

<table><thead><tr><th width="152.55078125">Icon</th><th width="137.59765625">Stage</th><th>Explanation</th></tr></thead><tbody><tr><td><img src="/files/seXtmvNPDjiFoD19QvlY" alt="" data-size="line"></td><td>Queued</td><td>This process is still waiting to be run.</td></tr><tr><td><img src="/files/BWwFrgzpf7hxqwvTGt11" alt="" data-size="line"></td><td>Completed</td><td>This process has been run, the system will tell you exactly when the process finished.</td></tr><tr><td><img src="/files/REuuqB4eSeYZcQn8Y4IW" alt="" data-size="line"></td><td>Failed </td><td>The process didn't run. There may be an error which needs to be addressed (such as incorrect parameters or no results), and it may need to be run again.</td></tr></tbody></table>

### Viewing a Process

To view a process, use the ID or Name to open it and access summary information. For Failed processes, this may include an explanation if available.


---

# 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://docs.cw.crisisworks.com/concepts-and-fundamentals/on-a-computer/your-user-profile-and-duties/background-processes.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.
