All videos

Runs and logs · 2:23

Find out why something did not work

Ask Chat why a run went wrong, check it in Logs, and test the fix.

Transcript

0:01Welcome

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

0:08Ask Chat first

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

0:21Nothing happened

For example, nothing happened at all. Chat finds the event that arrived, and compares its type with the one the first job listens for. Also check that the workflow is live. A paused workflow starts no runs until you resume it.

0:38A step did not run

Or one step did not run. That is not an error. The event did not match the job's Filters. A finished run does not mean every path ran. Open each job to see which paths ran.

0:51The answer is wrong

Or the answer is empty, or wrong. Chat compares what the job received with what it returned. An empty answer often means a detail was missing. The job expected the message text, but the event did not include it.

1:06Check it yourself

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. Open a run to see each job. A job can succeed, fail, or not run. On a failed job, Explain in chat asks Chat to look at it for you. In Activity, the Events tab lists every event that arrived.

1:35Ask Chat to fix it

Once you know what went wrong, ask Chat to fix it. Describe the problem in your own words. Chat saves the fix to a draft. The live workflow keeps running as before until you choose Go live. If the fix is not right yet, give Chat more context, like the message that failed or what the answer should have said. Test the draft with the same event that went wrong. When it looks right, choose Go live, and watch the next live run.

2:08What comes next

You now have the full loop. Describe the task, build it, check it, put it live, and improve it over time. When you want to go further, the documentation covers every detail.