Monitor flows

Use Flow Monitor to see what needs attention, how each flow version performs against its SLA, where time goes in a flow, and what one instance is doing.

Flow Monitor shows the instances of every published flow in the tenant. You need pulse.view. Open the app launcher and select Flow Monitor; the left menu has Monitor, Instances and Incidents. Read the Flows tab# Needs attention: the number of open incidents, of SLA breaches and the age of the oldest open instance. Each figure is a link to the matching list. Nothing needs attention means none of them applies. The table has one row per flow version, worst first: Running instances, open Incidents, P95 vs target (the 95th-percentile duration of completed instances against the SLA, with the verdict on target, at risk or breached) and SLA breaches. No SLA means the flow has no Flow SLA. 24 h, 7 d and 30 d set the window for every tab. Include debug runs adds debug versions and their instances, which are left out otherwise. Live means the page updates on its own as instances change. The SLA is the Flow SLA you set on the flow in Flow Studio (for example PT8H), and a step's own Target duration where one is set. See where time goes in a flow# Select a row on the Flows tab to open that version. The summary line shows completed instances (and per day), P50, P95 against the target, interventions per 100 instances, and Running by age (under 1 h, 1–24 h, 1–7 d, over 7 d). Heatmap colours each element by Frequency (how many runs) or P95 duration. A hatched element has Not enough data (fewer than 20 runs). A red badge counts the element's incidents. The table below lists each element's Runs (including the ones still running), P95 vs target and Incidents. Find instances# Open the Instances tab. Filter by Status (Running, Completed, Failed, Canceled), Version, business key (the search box), Started from and Started to, or tick Has an open incident. Select a row to open the instance. To act on several running instances at once, tick them and choose Retry incidents, Migrate or Cancel instances. See Run a bulk operation. Read an instance# The instance page shows the version the instance is pinned to (for example v1 (pinned)), who started it and when, and its live diagram: Elements that ran have a solid outline; paths not taken yet are dashed. The element where a token waits is highlighted. An element with an incident is red and carries a badge. Its incident is shown above the diagram; see Resolve incidents. The tabs below the diagram: Tab Shows Timeline Each element run, newest first: Attempt, Outcome, Started, Took and Error. Variables The instance's variables as JSON, including each task's outcome and output. Children Instances started by a call activity. Jobs The jobs of robot tasks, with Open job to go to the job in Orchestrator. Tasks The Action Hub tasks of user tasks, with Open task. Select the Flow Studio icon next to Live to open the flow in Flow Studio. Suspend, resume or cancel an instance# You need pulse.edit. Suspend stops tokens from moving. A job or task that already started goes on, and its result is taken when you resume. You can edit variables while the instance is suspended. Resume continues a suspended instance. Cancel instance ends the instance. Next steps# Resolve incidents Migrate and change running instances

Read the Flows tab

See where time goes in a flow

Find instances

Read an instance

Suspend, resume or cancel an instance

Next steps