# Automation Audit

The Automation Audit log records every execution of an automation rule configured in the Designer. Use it to verify that automations are firing as expected, troubleshoot failures, and audit what actions were taken for a specific patient or event.

***

## What the Automation Audit shows

Each entry in the Automation Audit includes:

* **Action Name** — the name of the automation that fired
* **Environment** — which environment the automation ran in
* **Status** — whether the automation succeeded, failed, or is pending
* **Event Name** — the triggering event (e.g., patient phase change, assessment completed)
* **Event Entity** — the object that triggered the event (e.g., the specific patient or CDT record)
* **Action Type** — what kind of action the automation performed (send message, create task, update CDT, etc.)
* **Patient** — the patient the automation ran for
* **Timestamp** — when the automation fired

***

## Filtering the Automation Audit

You can filter the audit log by:

* Action Name
* Environment
* Status (Success, Failed, Pending)
* Event Name
* Event Entity
* Action Type
* Patient

***

## Viewing event details

Click the **+ icon** to the right of any audit entry to open a JSON file containing the full event payload — including input data, output data, and any error messages if the automation failed.

***

## Common troubleshooting scenarios

**Automation didn't fire** — Filter by the automation name and check if there are any entries at all. If there are none, the trigger condition may not have been met.

**Automation fired but failed** — Click the + icon on the failed entry to review the error details in the JSON payload.

**Automation fired on the wrong patient** — Review the Event Entity and Patient fields to confirm the trigger data is correct, then review the automation conditions in the Designer.

***

## Postponed automations

Automations that include a time delay will show as **Pending** in the Automation Audit until the delay period elapses. To monitor and manage pending delayed automations, see [Postponed Tasks](/admin/security/postponed-tasks.md).

***

## Related articles

* [Admin Portal Overview](/admin/admin.md)
* [Postponed Tasks](/admin/security/postponed-tasks.md)
* [How to Create Automations](https://github.com/welkincloud-io/welkin-docs/blob/master/kb/designer/designer-how-to-create-automations.md)
* [Create Advanced Automations](https://github.com/welkincloud-io/welkin-docs/blob/master/kb/designer/create-advanced-automations.md)
* [Security Audit](/admin/security/security-audit.md)


---

# Agent Instructions: 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:

```
GET https://docs.welkinhealth.com/admin/security/automation-audit.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.