Start in the Runs tab
Go to Workflow automations → Runs and look for a row at around the time the event happened. What you find there splits the problem in two: either there's no run, or there's a run that skipped.
Find the row at the time your event happened. A single event can produce several rows — one per rule triggered by it.
There's no run at all
No run means the trigger never fired. Check:
Is the trigger the right one? An automation triggered by Defect created won't react to an inspection being submitted, even a failing one, unless that inspection raised a defect. If you want to act on the inspection itself, the trigger is Inspection submitted.
Did the event actually happen? An inspection saved but not submitted won't trigger anything.
Did the automation exist yet? Rules act on events from the moment they're created. Anything that happened before you saved it won't be picked up.
The run says Skipped
This is the common one, and it means the trigger fired but a condition ruled the event out. Open the automation and check each condition against what actually happened:
Condition | What to check |
Inspection has passed or failed | Was the inspections overall result really what you set? |
Submitted on a specific form | Was it submitted on one of the selected forms? Forms with similar names are easy to mix up, particularly if you have per-site versions. |
Submitted on a specific asset | Is the asset in the list? Newly added vehicles won't be unless you've added them. |
Defect ahs a specific severity | What severity the defect actually given? If it came from a diagnostic code, the severity may not be what a person would have chosen. |
Defect is on a specific asset | Same as above -check the asset in the selected list |
Remember that every ticked condition has to be satisfied. It only takes one to skip the run, so check them all rather than stopping at the first that looks right.
It ran but didn't do everything
Check which actions are actually ticked on the automation — it's easy to set up a rule with the severity action in mind and forget to tick the out-of-service one.
If an action is ticked but had no visible effect, look at whether it had anything to act on. Update severity of all defects does nothing visible on an inspection that raised no defects, and the run will still show as having gone ahead.
It didn't act on older records
Automations don't reprocess history. If you build a rule today, yesterday's failed inspections stay as they are. Anything you need changed on existing records has to be done by hand.
Still stuck
What to send us
The automation's name.
The date and time of the event you expected it to act on.
What you expected to happen, and what happened instead.
Whether a run appears in the Runs tab at that time, and its status.