1. This video shows how to find out why a workflow did not do what you expected, and how to fix it.
Workflows

Find out why something did not work

Ask Chat, check the run, and fix it safely.

Why did this run fail?
Auto
  1. You can always ask Chat why something did not run. Say what you expected, in your own words.
  2. Chat reads the workflow's runs and events, and tells you what it found.

Ask Chat why

Chat reads the runs and events

Customer requests
A customer wrote in, but no reply was drafted. Why did this not run?
Working..
Completed · 2 steps
I checked the runs and events for this workflow. The email arrived, and the run stopped at Draft a reply because the model returned no reply.
Customer requests
Type or @ to tag
A customer wrote in, but no reply was drafted. Why did this not run?
Auto
PublishedLive
Email received
Sort the request: damaged item, delivery question, return or refund.
Write a friendly reply to the customer's email.
Run workflowLogs
  1. For example, nothing happened at all.
  2. Chat finds the event that arrived, and compares its type with the one the first job listens for.
  3. Also check that the workflow is live. A paused workflow starts no runs until you resume it.

Nothing happened

Chat compares the event type

Is it live?

Customer requests
A customer wrote in at 10:41, and nothing happened.
Working..
Completed · 2 steps
A Message received event arrived at 10:41. Your first job listens for Email received, so nothing started.
Customer requests
Type or @ to tag
A customer wrote in at 10:41, and nothing happened.
Auto
PublishedLive
PublishedLive
PublishedRuns when the workflow is triggered.Pause
Email received
Sort the request: damaged item, delivery question, return or refund.
Write a friendly reply to the customer's email.
Run workflowLogs
  1. Or one step did not run. That is not an error. The event did not match the job's Filters.
  2. A finished run does not mean every path ran. Open each job to see which paths ran.

One step did not run

Finished is not every path

Customer requests
Why did Tell #support not run?
Working..
Completed · 2 steps
Its Filters need a refund request. This email is about a damaged item, so the job did not run.
Customer requests
Type or @ to tag
Why did Tell #support not run?
Auto
PublishedLive
Email received
Sort the request: damaged item, delivery question, return or refund.
Tell #support about refund requests.
Run workflowLogs
  1. Or the answer is empty, or wrong. Chat compares what the job received with what it returned.
  2. An empty answer often means a detail was missing. The job expected the message text, but the event did not include it.

The answer is wrong

Customer requests
The reply is about shipping, but the customer said it arrived cracked. Why?
Working..
Completed · 2 steps
The job received the sender and the order number, but not the message text, so it guessed.
Customer requests
Type or @ to tag
The reply is about shipping, but the customer said it arrived cracked. Why?
Auto
Input event
from: "Maya Chen"
order: "4821"
text: missing
Output event
Thanks for your order. Your sofa ships next week.
Not what was asked
  1. To see it yourself, open Logs, beside Run workflow. Each run shows when it started, its status, a short summary, how long it took, and what it cost.
  2. Open a run to see each job. A job can succeed, fail, or not run.
  3. On a failed job, Explain in chat asks Chat to look at it for you.
  4. In Activity, the Events tab lists every event that arrived.

Check it in Logs

Open a run to see each job

Or let Chat explain it

Every event is in Activity

Run workflow Logs
Logs Live Feed
All statuses Last 30 days
Started Status Summary Duration Cost
26 Oct 2026, 10:22:41Triggered runSucceeded All steps completedOutput event emitted 6.204s€0.0021
26 Oct 2026, 10:04:12Triggered runFailed Stopped at Draft a reply1 step completed 3.104s€0.0012
26 Oct 2026, 09:31:08Triggered runSucceeded All steps completedOutput event emitted 8.412s€0.0024
26 Oct 2026, 09:12:55Triggered runSucceeded All steps completedOutput event emitted 5.718s€0.0019
Logs Run resultsFailedMon, 26 Oct 2026, 10:04:12
Steps
Sort the request10:04:12Succeeded
Tell #support10:04:13Did not run
Draft a reply10:04:13Failed
Draft a reply
ExecutionInput & outputCost
Summary
StatusFailed
Execution time2.1s
Cost€0.0009
LLM Call - the model returned no replyExplain in chat
Execution logs
SystemInfoSystem log
Event context: tagged properties only (from, subject, body)
ActivityOverviewRunsEvents
Event typeIntegrationCreated at
Message receivedTeam chat10:41
Email receivedSupport inbox09:31
  1. Once you know what went wrong, ask Chat to fix it. Describe the problem in your own words.
  2. Chat saves the fix to a draft. The live workflow keeps running as before until you choose Go live.
  3. If the fix is not right yet, give Chat more context, like the message that failed or what the answer should have said.
  4. Test the draft with the same event that went wrong. When it looks right, choose Go live, and watch the next live run.

Ask Chat to fix it

The fix goes to a draft

Not right yet? Give more context

Test with the same event, then go live

Customer requests
The customer said it arrived cracked, but the reply is about shipping. Fix the reply.
10:48
Working..
Completed · 2 steps
Workflow edited successfully.
1 change applied:
Draft a replyEdited
Second try
Still wrong. The customer wrote "My lamp shade arrived cracked." Offer a new shade.
10:51
Working..
Completed · 2 steps
Workflow edited successfully.
1 change applied:
Draft a replyEdited
Made 1 change
Keep changesReject changesView changes
Made 1 change
Keep changesReject changesView changes
Customer requests
Type or @ to tag
The customer said it arrived cracked, but the reply is about shipping. Fix the reply. Still wrong. The customer wrote "My lamp shade arrived cracked." Offer a new shade.
Auto
PublishedLive Edit Customer requestsDraft Go live
Editing a draft. Published version unchanged.
Maya Chen's email Email received
Sort the request: damaged item, delivery question, return or refund.
Write a friendly reply to the customer's email.
Run workflowLogs Running workflow1sLogsStop watching Run completedin 3sLogs
LogsLive Feed
StartedStatusSummary
26 Oct 2026, 10:55:30Triggered runSucceeded All steps completedOutput event emitted
26 Oct 2026, 10:52:10Test runSucceeded All steps completedOutput event emitted
26 Oct 2026, 10:04:12Triggered runFailed Stopped at Draft a reply1 step completed
  1. You now have the full loop. Describe the task, build it, check it, put it live, and improve it over time.
  2. When you want to go further, the documentation covers every detail.
What comes next

You have the full loop

Each run shows you what to improve next.

Describe
Build
Check
Put live
Improve