Hi everyone,
we’ve noticed that in a few cases, Cadences don’t stop even though the contact replied (setting “stop on reply” is active).
It works fine most of the time, but occasionally the reply is visible in CRM without stopping the Cadence.
Our assumption is that this might be related to reply detection (threading), for example:
- reply not in the original thread
- different email address used
- forwarded email being answered
- reply logged but not linked to the Cadence step
Has anyone else experienced this?
Is this a known limitation or expected behavior?
Thanks!