What is an automation audit log?
Each time a flow is triggered, it saves a log of data that admins can audit to see when the flow was triggered, the status of its execution, and the details of each step the flow attempted to perform.
Reviewing audit log activity is an effective way to debug flows.
Automation audit logs store activity from the past 90 days. Older entries are automatically deleted and can't be recovered.
Admins can view the audit log of an individual flow, or a table of recent activity for all the flows in a space or app.
Each flow execution in the audit log displays:
Date & time: when the flow was triggered
Audit log ID: the unique identification number for a specific flow execution
Flow: the name of the flow
Status: the outcome of the flow execution
Total time: the flow’s total run time + processing time
Each log can be expanded to show the details and run times of each step in the flow.
Processing time isn’t shown. To calculate the processing time, add up the run time of each step in the flow and subtract it from the Total time in the audit log table.
Here are some scenarios that contribute to longer processing times:
The flow has a Delay action – the length of time the flow is paused counts as processing time rather than run time
The flow has a Send web request action – the time spent waiting for the web request counts as processing time
The flow requires interaction with external systems that are slow
The flow has multiple branches – branches run concurrently but count separately toward processing time
If 3 branches each take 1 minute to run, the total processing time is 3 minutes even though only 1 minute has passed.
Was this helpful?