Detail and runs

Tapping an automation opens its own screen, titled with the automation's name.

An approval comes first

If the automation is waiting on you, the approval is the first thing on the screen, above everything else, outlined and labelled Waiting for you. Where more than one is waiting, each is numbered.

It is the only thing on the screen most people can act on, so it sits above the configuration rather than under it. See Approvals.

The header card

The name, what triggers it in plain language, whether it is enabled, its description, and one line of health: Working, with when it last ran, or the reason the last finished run did not work.

That one line is the whole of it. A success rate would have to be counted across every run an automation has ever had, and the phone only holds the recent ones, so the screen says whether the thing is working rather than putting a number on it that would move as you scroll.

Test it now

Test it now runs the automation immediately. It asks for confirmation first, because it runs against the agent's most recent meeting and it runs even while the automation is disabled. After confirming, the screen switches to Activity so you can watch it.

The confirmation says whether a recent meeting was found, which matters: without one, some steps have nothing to work on and are skipped.

Owners and admins only. A member pressing it to find out what an automation does would fire a real run, CRM writes included, which is the wrong way to answer that question.

Overview tab

What it uses. The settings this automation was created with, each with its field name next to its value: which agent, which entity, which knowledge store, who approves. References are resolved to real names and avatars rather than shown as identifiers.

How it works. Collapsed, and it says how many steps there are and that your admin set them. Open it for the chain of actions in the order they run, each described in plain language. Steps come from the template and cannot be changed on the phone.

If the automation was built from a template your organization no longer has enabled, the screen says some settings cannot be shown here rather than naming the template that is missing.

Activity tab

Every run, newest first, updating itself while any run is still going and settling when they are all finished. Each row is when it ran and what happened. How long it took is on the run itself.

Where your deployment has no run history available, the tab says there is no activity yet.

A single run

Tapping a run opens it: its status, how long it took, its timestamps, and a link back to the automation.

Below that, the stages, one per action. Each stage shows its label, its status and its duration, and expands to show what went into it, what came out, and any error. That is where you look when an automation did something you did not expect.

A run sitting at Waiting for you shows the approval it is blocked on right there, so the run can be unblocked from the screen you are already looking at.

Status labels are listed in Reference.