Watch workflow runs and fix a paused workflow

Every time a workflow fires, Mesy records a run with one line per step. You read them on the Runs tab of a saved workflow. The Workflows list shows each workflow’s latest run under Last run.

Read the run history

Open a workflow and click Runs. Until it fires or someone presses Run, the tab shows No runs yet. Each row shows the run’s state, when it started, what triggered it, and the workflow version it used. A manual run adds Run by and the name of the person who pressed Run. The tab shows the 100 most recent runs and says so when there are more.

A run is in one of eight states: Running, Succeeded, Skipped, Waiting, Awaiting approval, Rejected, Cancelled or Failed. Click a row to expand its step list. Each step shows its outcome and a detail line, such as the condition that stopped a check or the reason it failed. A step that staged something for you carries a Review in Approvals link. A record you aren’t allowed to see appears as Restricted.

Understand the gate badges

In the editor, every action card carries a badge resolved from the workspace’s AI permission tiers and the owner’s role. Hover over it to read the reason.

• Runs automatically: the assistant that owns this action is trusted to write on its own at the current tier.
• Stages for your approval: the step creates a card for the owner to confirm instead of acting. Template emails and both AI actions always stage, at every tier.
• May stage (the badge adds “per record”): the update could overwrite existing long text. Mesy decides per record at run time, and an empty field fills automatically.
• Blocked: the step can’t run. Either the assistant is set to Read-only (tier 1), or the action needs a higher owner role.

An admin raises a tier under AI Permissions in Admin, so a tier block still saves. Assign the owner needs a manager or admin owner, and that block won’t save until you reassign the workflow or change the step.

Why a workflow pauses itself

Mesy switches a workflow off in two situations. After five failed runs in a row, the list shows Paused after repeated failures. The editor adds a red banner with a See the failing run link. Only failures count towards the five; a success, skip, rejection or cancellation resets the streak.

When the owner’s account is removed from Mesy, Mesy disables the workflow and the list marks it as disabled because the owner was removed. An owner who is deactivated but still listed makes each run fail, which leads to the same pause.

After a pause, the owner gets a Workflow paused notification naming the workflow and the number of failed runs. It can’t be muted. Clicking it lands on the workflow’s Runs tab.

Get it running again

To fix a workflow that paused after failures:

1. Open the workflow and click Runs.
2. Expand the newest Failed run and read the reason on the failed step.
3. Click Editor and change the step, the record or the permission that caused it.
4. Click Save if you edited anything.
5. Switch the workflow on with the toggle in the header, which now shows it as enabled.

Only the owner or an admin can use the toggle. For a workflow whose owner was removed, a member or manager reads that an admin must reassign it first. An admin picks a new owner under Reassign to… in the banner, then switches the workflow on. Mesy refuses to enable a workflow that has no owner.

Approve what a staged step proposes

AI: research & fill fields, AI: draft an email and Send a template email never act on their own. The run pauses in Awaiting approval. The owner gets a Workflow proposals notification saying the workflow staged a proposal for review, and clicking it opens the card on the Approvals page.

A staged email shows as Workflow email · review and send below, with a From workflow button that jumps back to the run. Sending it resumes the run; dismissing it settles the run as Rejected. If the workflow was switched off after staging, the card warns you before you send. Switching a workflow off keeps its staged cards.