> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/cerby-web-app/automation-log/filter-jobs-in-the-automation-log.md).

# Filter jobs in the Automation Log

This article describes how to filter jobs in the Automation Log using the Cerby web app.

{% hint style="info" %}
**Who can use this feature?**

* Workspace **Owners**, **Super** **Admins**, and **Admins**
* Only supported using the Cerby web app
  {% endhint %}

As a workspace **Owner**, **Super** **Admin**, or **Admin**, you can narrow down the jobs displayed in the [Automation Log](https://help.cerby.com/getting-started/concepts/audit-and-activity/automation-log) by applying the filters on the top menu.

These filters help you isolate specific automation jobs based on job type, status, and app. Filtering enables you to monitor large activity volumes, troubleshoot issues, or review recent identity, access, and account management changes.

To filter jobs in the Automation Log, you must complete the following steps using the Cerby web app:

1. Log in to your [Cerby](https://app.cerby.com/) workspace.
2. Select the **Automation** option from the left navigation drawer. The **Automation Log** page is displayed.
3. Apply any of the following filters located at the top of the page:
   * **Filter by status:** The following are the statuses you can filter the results by:
     * **Not completed:** If even a single nested job fails.
     * **Retrying:** If a single nested job is retrying.
     * **Running:** If a single nested job is still running.
     * **Started:** If nothing is running, but at least one nested job has started.
     * **Queued:** It is the default state if no jobs have started.
     * **Completed:** Only if all nested jobs are finished successfully.
   * **Filter by task:** The following are the tasks you can filter the results by:
     * **Adding users:** It involves creating a user account and inviting a new user to a seat-based or paid social app.
     * **Syncing users:** It involves retrieving the user and asset data from a seat-based or paid social app.
     * **Updating user roles:** It involves updating the existing role of a user within a seat-based or paid social app.
     * **Removing users:** It involves removing users from a seat-based or paid social app.
     * **Rotating passwords:** It involves rotating the password of an account.
     * **Turning on MFA:** It involves turning on multi-factor authentication (MFA) for an account with a Cerby-managed method.
     * **Turning off MFA:** It involves turning off MFA for an account.
   * **Filter by app:** The Cerby-managed apps and integrations, you can filter the results by.

Now you are done.


---

# 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.cerby.com/cerby-web-app/automation-log/filter-jobs-in-the-automation-log.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.