The Runs tab
Go to Workflow automations and select Runs. Every time a trigger fires, a row is added — whether or not the automation went on to do anything.
Runs are listed newest first, with the time shown both as a date and as how long ago it was.
Column | Shows |
Status | What happened on this run. |
Automation | Which rule was triggered. |
Trigger | The event that started it. |
Executed at | When it happened. |
Note that a single event can produce several rows. If three of your automations are triggered by defects being created, one new defect creates three runs — one per rule, each evaluated independently.
What Skipped means
Skipped is the status you'll see most often, and it isn't a problem.
It means the trigger fired but the conditions weren't met, so the automation correctly did nothing. A rule limited to your accident report form will skip every other inspection submitted that day. That's the rule working — it's filtering out the events you told it not to act on.
A long list of skipped runs isn't a sign that something is broken. It's usually a sign your conditions are doing their job.
search
If you expected a rule to run and it shows as skipped, one of the conditions ruled the event out. The usual cause is a condition that's narrower than you intended — the wrong form selected, or an outcome set to failed when the inspection actually passed.
Deleted automations
Rules you've since deleted still appear in the run history, marked as deleted. Their past runs aren't removed, so the history stays complete and you can still account for something that happened weeks ago under a rule that no longer exists.
Where actions appear on the record
Anything an automation does is recorded in the same place it would be if a person had done it. The difference is the actor: entries show Workflow Automations rather than a user's name, so you can always tell which changes were automatic.
The out-of-service log
For assets, open the Out of service tab. It shows the full history as a timeline: each time the asset came off the road, who took it off, why, and how long it stayed there. Totals for days out of service and number of times sit at the top.
Automatic entries sit in the same timeline as manual ones. The reason set on the automation is carried through word for word.
Select Download log if you need the history as a file — for a compliance record or an audit, for instance. Automatic and manual entries are included together.
history
Deleting an automation doesn't undo anything it already did. Records it created stay exactly as they are.