Hi everyone,
I built a flow that's supposed to collect the user's phone number before sending them further messages/content. However, it seems the flow is skipping the phone number request step entirely and sending the message directly, without ever prompting the user to enter their phone number.
Looking closer at the flow logic, I think I found the issue: I have a Condition step that checks "Phone# is unknown" after a "Waiting for phone from contact" action. But it looks like BOTH branches — the one where the contact never responded/phone is unknown, AND the one where the contact doesn't match any conditions — eventually merge back into the same Action step and continue into the same next automation. So contacts who never gave their phone number are being treated the same as contacts who did, and both get pushed forward into the next automation/message.
Out of ~18,600 people the message was sent to, only 97 actually responded with a phone number — so this branching issue is affecting the vast majority of contacts.
Additionally, I'm noticing delays in the flow — messages/actions aren't triggering as fast as expected.
Has anyone run into this before? Is this expected behavior with the Condition/branching logic, or am I missing something in how to properly separate "phone number received" vs "phone number not received" paths so they don't converge?
Any troubleshooting steps or fixes would be much appreciated. Thanks in advance!
