Detail and runs
What an automation is configured for, its steps, running one on demand, and reading a run stage by stage.
Tapping an automation opens its own screen, with a header card and two tabs.
The header card
The name, what triggers it, whether it is enabled, how many times it has run, its success rate across the runs that have loaded, and a count of approvals waiting on you.
Run now
Run now runs the automation immediately, on demand. 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 the Runs tab so you can watch it. The confirmation message tells you whether a recent meeting was found, which matters: without one, some steps have nothing to work on and will be skipped.
Details tab
Three things:
What it does. The description.
What it runs for. The settings this automation was created with: which agent, which entity, which knowledge store, who approves. References are resolved to real names and avatars rather than shown as identifiers.
Steps. The chain of actions in the order they run, each labelled in plain language. Steps come from the template and cannot be changed on the phone, and the screen says so rather than offering controls that do nothing.
If the automation was built from a template your organization no longer has enabled, the screen says the template is unavailable instead of showing an empty configuration.
Runs tab
Every run, newest first, updating itself while any run is still going and settling when they are all finished.
Run history depends on how your deployment is configured. Where it has not been set up, the tab explains that run history is not available yet rather than showing an error.
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. See Approvals.
Status labels are listed in Reference.