Setting the trigger to office hours does not keep every later step inside the same window. Waits change the time of execution.
Choose a timezone owner
Write down whether the window follows the business, a team location or each recipient. A time without a named timezone is an ambiguous automation rule.
Keep that choice in the workflow record so an operator can explain why a message is waiting. Avoid silently changing the rule when a server moves regions.
Check each send step
After a wait completes, evaluate the permitted day and time again. If the window is closed, keep the task pending for an allowed execution time.
Miss Blue’s public guide describes business-hours gating for each message and says the switch is off by default. A buyer should enable it deliberately and inspect the selected timezone and days.
Keep observing replies while held
A scheduling hold should not prevent the workflow from learning that the customer replied. Re-evaluate the reply condition before releasing a held message.
The documented Miss Blue behavior counts overnight replies. A custom implementation should preserve the same business intention even if its timers use another design.
Give stale reminders an expiry
A reminder released after a long outage or holiday may no longer make sense. Add a business validity window as well as a clock window.
The simulator’s “closed” state represents a hold, not a computed calendar date. Test real weekends, daylight-saving changes and outages against the scheduler you deploy.