chatleadr Docs
Open Chatleadr

My Workflow Stops and Says Nothing

Work down the list in order. Each check is quicker than the one after it.

Error port empty API Request: look up the order Success Error Nothing is sent. Nothing is logged as an error. The visitor sees silence. Recorded as completedIt counts toward your success rate in analytics. Error port connected API Request: look up the order Success Error Message: “I couldn’t reach that system” End, completion status Failure Recorded as a failureThe visitor can act, and the number is visible.
The same failure, twice. On the left the error port is empty and the run stops silently, recorded as a success. On the right it leads somewhere.

1. Check the Port the Run Left By#

Open the workflow and look at the node the run reached last. A port with no wire leaving it ends the run there, and the editor draws that port as a hollow dot.

An API Request that failed leaves by its Error port, a Form the visitor closed leaves by its Cancelled port, and a Function that threw leaves by its Error port. With those three ports empty, all three look the same from the visitor's side.

Connect every Error and Cancelled port to something, even if that something is one Message node apologising and an End node set to Failure. That turns an invisible stop into a conversation the visitor can act on and a number you can see.

2. Read the Execution Log#

The log lists each run, the node it reached and where it stopped. Find the run, read the last entry, then go back to the canvas and check that node's ports. A workflow that starts and stops at an API node looks the same to a visitor as one that never started at all.

3. Check the Warning Badge on the Canvas#

Missing Connections appears in the editor whenever a node has no outgoing wire, or a Decision node has a port left unwired. It does not stop you saving, so a workflow can be live with the badge showing. See using the workflow editor.

4. Check for a Loop With No Way Out#

A run stops after 100 nodes wherever it has got to. The execution log records Execution exceeded the 100-step limit; the flow likely contains a loop. and analytics counts a failed execution. A loop is supported, so the repair is to add a Decision that can leave it rather than to unwire the loop. See execution limits.

5. Check How Long the Visitor Took#

A paused run waits 10 minutes for an answer by default, and a whole run has 20 minutes from start to finish. A visitor who opens a form and answers it the next morning resumes nothing.

Raise Idle Timeout (Minutes) and Total Run Time (Minutes) on the workflow where a long wait is intended. A Form node's secure link stays valid for one hour, which is longer than the idle default the run itself is held to, so both ceilings have to cover the wait or the answer arrives too late to use.

What to Send Support#

Email support@chatleadr.com with three things:

  1. The bot name and the workflow name.
  2. The execution log entry for the run, including the last node it reached.
  3. What the visitor saw instead.

Common Questions#

The Run Says Completed and Nothing Was Recorded. Why?#

A run that ends on an empty port never reaches an End node, and in a workflow an End node is the only thing that saves a lead or sends it to your integrations. The run still finishes as completed. See how a lead is captured.

The Workflow Works in the Preview and Stops on My Site. What Is Different?#

The preview runs the bot you have open, and a live page runs whichever bot key is in its snippet. Check the key in the install snippet before looking at the workflow again.

Does an Empty Port Show as an Error in Analytics?#

No. The run is counted as a success, so a workflow with an empty port reads as healthy on the analytics page while visitors reach nothing.