Bug? Editing a timed step in a live automation doesn't update contacts already in that step β plus no bulk removal
Has anyone else run into this?
We discovered that when contacts are actively waiting at a delay or timed step in an automation, editing that step doesn't update them. The change only applies to contacts who reach the step after you save the edit. Contacts already queued there stay locked to the original datetime β even if you change it in the automation.
Setting the funnel to Draft doesn't help either. The pending actions still fire on the old schedule regardless of funnel status.
As best we can tell, here's what's happening under the hood: when a contact enters a timed step, FluentCRM calculates the datetime and writes it as a scheduled action record in the database. Editing the automation only updates the funnel template β it doesn't touch those already-written records. So contacts in an active step are essentially hardcoded to the original date.
Future steps work fine (edits apply correctly) because their scheduled actions haven't been created yet.
The related problem: there's no bulk way to remove contacts from an automation. You can remove them one at a time from the subscriber list, but there's no bulk action. So you can't cleanly pull everyone out and re-enroll them under the corrected funnel.
Our workaround for 2,500 contacts in an automation:
Duplicate the automation with the corrected step.
Re-enroll affected contacts in the new campaign.
In the old campaign, add a "Cancel Automation" step right after the timed step β so when the old actions fire, contacts immediately exit.
It works, but it's not a great solution when you just need to shift a date on a live campaign.
Has anyone found a cleaner fix? We've also created a support ticket. If you've hit the same issue, worth replying here β the more context FluentCRM has, the easier it is for them to prioritize.
I had the same issue a few times, I didn't know how to work around it and support simply advised against editing the Wait steps. Thank you for sharing your work around.
Thanks. Hopefully it will be fixed soon.