What is an automation audit log?
Each time a rule is triggered, it saves a log of data that admins can audit to see when the rule was triggered, the status of its execution, and the details of each step the rule attempted to perform.
Reviewing audit log activity is an effective way to debug rules.
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 rule, or a table of recent activity for all the rules in a space or app.
Each rule execution in the audit log displays:
Date & time: when the rule was triggered
Audit log ID: the unique identification number for a specific rule execution
Rule: the name of the rule
Status: the outcome of the rule execution
Total time: the rule’s total run time + processing time
Each log can be expanded to show the details and run times of each step in the rule.
Processing time isn’t shown. To calculate the processing time, add up the run time of each step in the rule and subtract it from the Total time in the audit log table.
Here are some scenarios that contribute to longer processing times:
The rule has a Delay action – the length of time the rule is paused counts as processing time rather than run time
The rule has a Send web request action – the time spent waiting for the web request counts as processing time
The rule requires interaction with external systems that are slow
The rule 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.
この内容はお役に立ちましたか?