November 2026 - Automation Execution Log
See every automation run, and trace any automated task back to where it came from.
What's New
Your automations are already working behind the scenes, creating follow-up tasks when documents stall so nothing gets missed. Now you can see all of that work. Every automation has a new Execution Log that shows each time it ran, whether it succeeded, which document it acted on and what it did.
Open any run to see the trigger, conditions and actions it used at that moment, even if the automation has been edited since. Each automation card also shows how many times it ran in the last 30 days and who last edited it.
And when an automated task lands on someone's list, it's labelled as created by skubot. Anyone on your team can select the label and click View details to see exactly which automation created it, and why.
Automation Engine is available on Advanced and Enterprise plans. Admins set up and manage automations, and anyone on your team can view the Execution Log.
Why It Matters
Admins set up automations and managers rely on them, but the whole team feels the impact. With the Execution Log:
- Admins can confirm each automation is doing what it was set up to do
- When a run fails, you can see why and fix the setup yourself
- Reps always know where an automated task came from and why it was assigned to them
- Past runs stay accurate, even after an automation is edited
Getting Started
To see what your automations have been doing:
- Click Automations in the left-hand navigation menu.
- On an automation card, open the menu beside Edit and select Execution Log. You can also open the automation and select the Execution Log tab.
- Filter by document number, date range or status, or sort by date, status or version.
- Select any run to see its details, or select the document number to open the record.
- On a task created by skubot, select the label and click View details to see the run behind it.
For the full walkthrough, read the help article.