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.
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
You can filter the audit log by:
Action Name
Environment
Status (Success, Failed, Pending)
Event Name
Event Entity
Action Type
Patient
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.
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.
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.
Last updated
Was this helpful?
Was this helpful?
