Dr Cog
Dr Cog4w ago

Global no-reply is broken - "ended after reaching unconnected path"

If global no-reply is set, and the delay is reached, it will immediately end the call before any no-reply message is sent. The debug message states "Ended after reaching unconnected path", suggesting that the no-reply response is not correctly integrated into the flow.
0 Replies
No replies yetBe the first to reply to this messageJoin

Did you find this page helpful?