Automation and flowsAbout 4 minutes

Inspect execution history and errors

See whether each run succeeded, read the error and suggested action, and jump back to the flow from there.

Sections in this guide

Find the run you need

1
Open the execution history.
2
Filter by status: completed, failed, needs review, processing, or waiting for user.
3
Choose a time range (last 24 hours, 7 or 30 days).
4
On each row, read the error and suggested action for that run.

Failed with a connection error means the page connection has a problem; check and reconnect the page.
Needs review means the run needs your decision; read the details and fix the flow.
Waiting for user is not an error; it means the user should reply next.
Use the link on the same row to jump straight to editing the flow.

Note:If no reply was sent but no run was recorded either, check the flow's start condition first.

Want to do it now?You will leave the guide and open the corresponding dashboard section.

See how many times the flow started, how far users progressed, and where review is needed.

A start condition determines which message, comment, or event should start the flow.