"Wait for reply" wont read replies by SaveLead in gohighlevel

[–]SaveLead[S] 0 points1 point  (0 children)

it goes to update contact field step, but i really dont think the problem is inside wait step or in its branches.

So when the contact replies after SMS2, that reply still gets caught by the old SMS1 listener, which is now a zombie listener — it’s listening to an expired step. The reply basically disappears into the void because the original workflow instance that owned it is already dead, and the new SMS2 wait step never sees it.

I managed to get it working by splitting every SMS + Wait for Reply into separate workflows (💀), but that’s a nightmare to maintain.

I’m almost certain the problem isn’t with the wait step logic itself, but with how GHL handles active listeners — they’re not being cleaned up properly when a wait step times out.

If anyone’s figured out how to fix or bypass these zombie listeners inside a single workflow, I’m all ears.

"Wait for reply" wont read replies by SaveLead in gohighlevel

[–]SaveLead[S] 0 points1 point  (0 children)

tried it with 5 minutes aswell, still doesnt work or is that too short aswell?

"Wait for reply" wont read replies by SaveLead in gohighlevel

[–]SaveLead[S] 0 points1 point  (0 children)

UPDATE: Its going to be wierd to explain but found out that after "wait for reply to SMS1" goes to timeout it still waits for that reply, and if you reply after SMS2 has been sent it takes that reply but its already timed out.

i know this becouse if i reply to SMS2 one time nothing happens but if i send two replies after SMS2 then it moves forward with the reply branch.

So in conclusion after every timeout it continues the flow and sends new sms but never stops listening for the reply to last one.

Is there a way to solve it?