They're part of the FleetAI add-on, available on Standard, Pro and Fixed Unlimited subscriptions. If Workflow automations isn't in your account, your customer success manager can tell you what's needed.

No, as long as your account has the Fleet AI add-on. Go to Workflow automations and select Add automation. There's nothing else to switch on first.

A couple of minutes. It's three steps: pick the event, pick the conditions, pick what happens. See Create your first automation

A failed inspection on your accident or incident report form, taking the vehicle out of service. It's narrow enough that it will only fire when you'd want it to, which makes it safe to switch on while you're still getting a feel for how automations behave.

No. An automation applies to events from the moment you create it. Anything already in your account stays as it is.

Two events: an inspection being submitted, or a defect being created. Defects count however they arose — from an inspection, added by hand, or reported by a diagnostic code.

No. Each automation has a single trigger. Build a second rule for the second event.

Three things, and you can choose more than one: mark the asset out of service with a reason you write, set every defect on the inspection to a severity, and create a work order.

Yes, and all of them have to be met for the automation to continue. There's no "or" — if you need one, build two rules. The exception is that some conditions accept several values at once, like selecting three forms on Submitted on a specific form.

The automation runs every time the trigger fires. That's rarely what you want. Work out roughly how often the event happens in your fleet in a normal week before leaving conditions blank.

The Runs tab lists every time a trigger fired. Actions also appear on the record itself — see Check what your automations have done.

Workflow Automations, rather than a person's name, so automatic changes are always distinguishable from manual ones.

Because the trigger fired but your conditions ruled the event out, so the automation correctly did nothing. A rule scoped to one form will skip every inspection submitted on a different form. It's the rule working, not failing.

Yes. Run history is kept, including for automations you've since deleted — those appear marked as deleted.

Check the Runs tab first. No run means the trigger never fired; a skipped run means a condition ruled it out. Why didn't my automation run? works through both.

That will be an automation. Open the asset's Out of service tab — the entry shows Workflow Automations along with the reason set on the rule. To find which rule, check the Runs tab around that time.

A condition is usually missing or broader than intended. Open the rule and check each condition against the events it acted on.

Not automatically. Put the affected assets back in service yourself, then narrow the rule's conditions before it runs again. Deleting the automation stops it running but doesn't reverse what it already did.

Yes. Open it from its card and edit any part of it. Changes apply to events from that point on.

It stops running. Anything it already did stays as it is, and its past runs remain in your history.

If you're planning a large number of rules, check with your customer success manager.

Build it as narrowly as possible to begin with — one form, or one asset — then watch the Runs tab for a few days to see exactly what it caught and what it filtered out. Widen it from there. Example automations covers how to do that safely.