Desired Architect - Inbound Message Flow Ending Without Disconnect Block

Hello everyone,

I have an Open Messaging integration working with Architect - Inbound Message Flow.
It is compulsory ending an architect flow with either TransferToACD, Disconnect or ChangeState block as far I can see.
My desire is doing the steps of architect flow blocks as expected and then ending it without an action so it can enter to the flow with every next inbound message again until my disconnect or TransferToACD conditions happen in it.
I can do that by ending the flow with Disconnect block, however it undesirably triggers every time my process/automation to detect the true conversation disconnect events.
Also, I tried ending the flow with Change State block by changing to Initial state. This worked better by not triggering every time disconnect event, however I think somehow error occures after some amount of time (about 10 minutes) in the flow by that and in the Error Handling I have to choose either one of Disconnect or TransferToACD again, so naturally I choose Disconnect and this action ending after about 10 minutes with Disconnect event again.

So my question is, which block I can end the architect flow with except Disconnect, ChangeState or TransferToACD blocks so it doesn't disconnect the conversation and enter the flow with every next inbound message?

Thanks in advance,

Regards

Duplicate

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.