Workflow settings: re-entry, stop on response, time windows
The Settings tab is what keeps automation polite — one run per contact, halt on reply, quiet hours, rate limits, bulk enrollment, and version restore.
Every workflow has a Settings tab. Five controls matter most:
Re-entry policy. “One active run per contact” (the default) means a contact who’s already mid-flow can’t be enrolled twice — the #1 protection against double-messaging. “Once ever” is for welcome-style flows; “every event” for logging-style flows.
Stop on response. When the contact replies on any connected channel — SMS, email, chat, WhatsApp — their active runs cancel instantly. A human took over; automation steps aside.
Time window. Messages only send between the hours you set; steps that come due overnight hold until the window opens. Waits and internal steps are unaffected.
Max runs per hour. A bulk event (CSV import, mass tag) can’t blast your channels: surplus runs queue and release gradually.
Bulk enroll + version history. Enroll everyone with a tag or pipeline stage (preview the count first — releases respect the rate limit and re-entry policy), and restore any previous version as your draft if an edit went wrong. Published versions are immutable; in-flight runs always finish on the version they started with.
And remember the Test button: it runs the whole flow with sends stubbed (nothing leaves the building) — only AI steps run for real so you can judge their output.