> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/system-activity/scheduler-audit-logs.md).

# Scheduler Audit Logs

**Scheduler Audit Logs** lists the background tasks the server queued for your workspace, such as notifications, archival, health check status and maintenance windows. For each one you see who ran it, when, its outcome and its full log. Use it to check that background work runs and to read the error when a task fails. This history does not start or retry work.

Open it from **Administration** → **System Activity** → **Scheduler Audit Logs** in the sidebar.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FSAkXtaDCVBco2rIaYilm%2Fv2-audit-scheduler.png?alt=media&amp;token=2ff6c13f-e631-4d26-815e-b4227ea16928" alt="Scheduler Audit Logs with status filter, handler search, time window and background jobs chart"><figcaption><p>Scheduler Audit Logs</p></figcaption></figure>

{% hint style="warning" %}
You need a role that can view the system audit log. On a multi-tenant installation, each tenant sees only its own background work.
{% endhint %}

## Filters

| Filter                 | Description                                                                                                                                                                                              |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Status**             | **All recorded statuses**, or one of **Scheduled**, **Pending**, **Executing**, **Downloading**, **Analyzing**, **Completed**, **Failed**, **Stopped**, **License quota exceeded**, **License expired**. |
| **Search handler key** | Finds tasks by name, for example `Archival`.                                                                                                                                                             |
| Time window            | **Last 24 hours**, **Last 7 days** (default), **Last 30 days**, **Custom range** or **All retained history**.                                                                                            |

**Background jobs created over time** charts matching and failed records per period. Click a bar to investigate that period. **Saved filters**, **Refresh** and **Export this page** work as on the other tabs.

## Background Work

Newest records first.

| Column              | Description                                                                                     |
| ------------------- | ----------------------------------------------------------------------------------------------- |
| **Handler**         | The task, for example "Maintenance Window Handler" or "User Subscription Notification Handler". |
| **Status**          | The task's recorded status.                                                                     |
| **Claimed by**      | The worker that ran the task. Empty until a worker claims it.                                   |
| **Created**         | When the task was queued.                                                                       |
| **Eligible to run** | The earliest time the task may run. Normally the same as **Created**.                           |
| **Finished**        | When the task finished.                                                                         |
| **Evidence**        | **Inspect log** opens the task drawer.                                                          |

| Status        | Meaning                                                                                                                                           |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Pending**   | Queued and waiting for a worker. Tasks normally stay pending for a few seconds; many pending tasks mean no worker is running or workers are busy. |
| **Executing** | A worker claimed the task and is running it.                                                                                                      |
| **Completed** | The task finished successfully.                                                                                                                   |
| **Failed**    | The task raised an error. Open its log to read it.                                                                                                |

## Inspect a Task

1. Click **Inspect log** on the row.
2. Review **Handler**, **Status**, **Claimed by**, **Work identity** and **Tenant**.
3. Under **Execution timeline**, see when the task was **Created**, became **Eligible to run**, was **Claimed by worker** and **Finished**. Only recorded timestamps are shown.
4. Under **Recorded log**, read the task's log, one line per event with a timestamp and a level such as `INFO`, `WARN` or `ERROR`. Use **Find a value or message in this record** to search it.
5. Click **Download evidence** to save the complete log.

## Next Steps

* [System Audit Logs](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/system-activity/system-audit-logs.md): find the operations people and agents performed.
* [Entity Archives](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/system-activity/entity-archives.md): see the records archival tasks saved.
* [System Activity](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/system-activity.md): the other tabs.


---

# 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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/system-activity/scheduler-audit-logs.md?ask=<question>&goal=<user_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.
