Activity statuses

Every row in Automation → Activity has a status. It tells you whether a flow's event led to agent work and, if so, how far that work has got. Use this page to understand each status and what to do next.

From event to run

When an event matches a flow, one of three things happens:

The run starts. Helpin launches the agent, and the row follows the run from Queued through to Completed, Failed or Cancelled.
The run is skipped. The flow matched, but Helpin decided not to start the agent. The row shows Skipped.
The launch fails. Something stopped the agent from starting. The row shows Failed with an error, and you can't open a run.

Events that don't match any flow don't appear in Activity at all.

Status reference

Status	Meaning	What to do
Queued	The run is waiting to start	Nothing, it will start shortly
Running	The agent is working	Open the run to watch progress
Paused	The agent is waiting for a person	Open the Needs you tab
Completed	The run finished	Open the run to check the result
Failed	The run, or its launch, stopped with an error	Hover over the status to read the error
Cancelled	Someone stopped the run	Nothing, unless it was a mistake
Skipped	The flow matched but no run started	See the reasons below

Paused runs

On the Needs you tab, paused runs show why they are waiting:

Label	What to do
Needs approval	Select Approve, or View run to review first
Needs your input	Select Respond and answer the agent's question
Needs sign-in	Select Respond and follow the prompt to authenticate

Why a run is skipped

The agent is already working on the same item. Helpin won't start a duplicate run.
A semantic condition didn't allow it. See the next section.
The run needed something the item didn't have, such as a delivery repository for a task.

Semantic condition results

If a flow has a semantic condition, Activity records each check as a Flow condition row with one of these results:

Result	Outcome
Condition matched — action may proceed	The action continues
Condition did not match — action skipped	The event didn't meet your condition
Condition was uncertain — action skipped	The event wasn't a clear match
Condition check unavailable — action skipped	The check couldn't run
Condition is in evaluation mode — action skipped	Conditions are being evaluated for your workspace and don't run actions yet
Event exceeds the condition input limit — action skipped	The event had too much content to check
Flow or task changed during the check — action skipped	The flow or task was edited while it was being checked

If many events are skipped as uncertain, rewrite the condition to be more specific.

Fixing failed launches

Common causes of a failed launch are a missing or deleted agent, an agent that can't work on the chosen target, or a target that no longer exists. Open the flow, check Using and On, and look for Missing agent or Setup incomplete. See Edit, pause and delete flows.

Was this article helpful?