Hello everyone,
I'm currently building a chat flow in Webex Connect Standalone and have encountered an unexpected behavior related to the Receive node.
Normally, the Receive node should capture and process actual messages typed by the user in the chat window. However, during testing, I observed that when I start typing a response (even without sending it), the Receive node immediately exits on the "successful" path — with a message content of "typing indicator". This seems to happen specifically when I press the spacebar while typing.
This behavior is causing issues with the flow logic. In my design, the Receive node is placed inside a loop, and after receiving a valid message, the flow routes back to a Scripted AI Agent node. But since the Receive node is triggered by a "typing indicator" event, the flow proceeds incorrectly. The AI agent receives the message "typing indicator", which it is obviously not trained to handle, and replies with a fallback message like "Sorry, I am unable to understand your message..."
My Questions:
- Is this behavior expected in Webex Connect Standalone?
- If so, is there a way to prevent the Receive node from reacting to typing indicators?
- Is there any configuration or workaround to filter or suppress these non-message events from triggering the flow?
Any insights or suggestions would be highly appreciated.
Thank you in advance.
Yes, I’ve implemented a loop that returns back to the same Receive node — and that does solve the issue with the typing indicator. However, I noticed that the Flow Builder doesn’t allow you to connect the Success path of a node directly back to the same previous node, most likely due to a built-in loop prevention mechanism.
To work around this, I added an intermediate node — in my case, a simple Evaluate node containing a minimal JavaScript expression. This acts as a pass-through and allows the loop to complete without any logic disruption.
However, it would be good to know, if there is another way to resolve it.
