> ## Documentation Index
> Fetch the complete documentation index at: https://docs.augmentcode.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage automations

> Review the schedules, webhooks, and events that trigger your Experts, and track each one's runs from a single page.

Find **Automations** under **Settings**. Select an Expert's name to open its detail page and review what triggers it, what it's received, and what it's run. The detail page has three tabs: **Overview**, **Run History**, and **Event History**.

<Tabs>
  <Tab title="Overview">
    The **Overview** tab displays the automation's Expert configuration and status together with its schedules, webhooks, and integration triggers. It shows the automation's name, description, **Enabled** or **Disabled** status, **Owner**, and number of **Enabled workflows**, plus a **Triggers** section listing each one.

    Use this tab to confirm which Expert configuration and triggers belong to the automation before investigating an event or run.

    ### Pause or remove triggers

    Use the controls in the **Triggers** section to manage a trigger:

    * Turn off the enable toggle to pause the trigger without losing its configuration. Turn it on to resume the trigger.
    * Remove the trigger to stop it from starting the Expert. Removing a trigger does not change the Expert's capabilities or tools.
    * Use **Auto-archive sessions created by this trigger** to choose whether trigger-started sessions remain visible after they become idle.

    <Note>Cosmos runs schedules one at a time. If the next fire arrives while the previous run is still going, Cosmos skips that fire instead of queueing it or running it later. See [Schedules](/cosmos/config-schedules).</Note>
  </Tab>

  <Tab title="Run History">
    The **Run History** tab lists sessions that a trigger started for this automation. Select a run to open its session and inspect what the Expert did. If the session has workers, its worker tree appears in the session's right sidebar.

    Above the run list, the **Last 24 hrs** and **Last 7 days** summaries show succeeded and failed run counts. Use the **My runs** / **All runs** toggle to switch between your runs and all runs you can access; the summaries and run list update to match the selected scope.

    <Note>**Run History** in the Automations sidebar shows runs across automations. Open an automation's detail page when you only want runs for its Expert.</Note>
  </Tab>

  <Tab title="Event History">
    The **Event History** tab displays recent events grouped by the automation's event-driven triggers. Each group identifies the trigger and source, then lists the matched event type and relative time.

    This tab is a best-effort view based on each trigger's source, event type, payload and header filters, and webhook identity. It does not present the full cross-automation Event Log — see [Inspect events across automations](#inspect-events-across-automations) for that view. Scheduled triggers do not receive inbound events, so they do not appear here.

    <Note>An automation with no event-driven triggers has no event history to show.</Note>
  </Tab>
</Tabs>

## Inspect events across automations

Open **Event Log** under **Automations** in the sidebar when you need to investigate events across all automations. The newest events appear first. You can:

* Filter by source, such as GitHub, GitLab, Linear, Slack, Webhook, or PagerDuty.
* Use **Advanced Filter** to filter by event type, JSONLogic payload filter, or header filter.
* Select an event to inspect its source, event type, timestamp, JSON payload, and captured request headers.

Use the global log to test a filter against payloads Cosmos has received before adding that filter to a trigger. See [Configuring triggers](/cosmos/config-triggers) for the event-type and filter reference.

## Related pages

* [Understanding automation](/cosmos/automations) explains how triggers, events, and Experts fit together.
* [Your first automation](/cosmos/first-automation) walks through creating two automations.