Business Day Logic Update: More Accurate Scheduling for Your Workflows

Business Day Logic Update: More Accurate Scheduling for Your Workflows

Hello everyone,


We’re improving how business-day calculations work in workflows, especially when triggers happen on weekends. This update ensures that offsets like +0, +1, and +2 business days behave exactly as intended, giving you clearer and more predictable automation timing.

When you create workflows that depend on business days, you usually add a offset next to a date field. This number decides when the workflow action should run.

To keep it simple:

  • +0 means the action should run immediately, but only within business hours.

  • +1 means it should run on the next business day.

  • +2 means two business days later, and so on.

 

In this setup, business days are Monday to Thursday. If something triggers on a weekend, it should wait until the next business day.


What the logic is expected to do

Suppose a customer registers on a Saturday. If you use business-day offsets, this is how it should ideally work:

  • +0 business days should run on Monday, since the weekend is skipped.

  • +1 business day should run on Tuesday.

  • +2 business days should run on Wednesday.

In other words, each number should push the action forward by one business day.


What the system was doing earlier

Right now, the system behaves a little differently when the trigger happens on a non-business day like Saturday. For example:

  • +0 goes on Monday, which is correct.

  • +1 also goes on Monday, which is not correct.

  • +2 goes on Tuesday.

This means the system was not separating +0 and +1 correctly for weekend triggers. They both ended up on the same day, even though they were meant to be different.


Why does this need a fix?

Business-day scheduling should give users clear and predictable timing. When +1 ends up behaving like +0, it can cause:

  • Emails or updates going earlier than expected.

  • Automations running ahead of schedule.

  • Confusion when reviewing workflow logs.

Correcting this ensures each offset behaves exactly as intended.

Let's consider a logistics company that sends follow-up emails one business day after a shipment request is submitted.

> A customer submits a shipment request on Saturday.

> The workflow is configured with +1 business day to send the follow-up email.





What users expect:

The follow-up email should be scheduled for Tuesday. Monday becomes the first business day after the weekend, and +1 should move it to the next business day.

What was happening earlier:

The email was being sent on Monday, because +1 was treated the same as +0 when the trigger happened on a weekend.

After the fix:

The email will now be sent on Tuesday, matching the business-day offset exactly. 



What this update means for you


This update does not break any workflows. It simply corrects the business-day calculation so schedules behave consistently.

You will see:

  • More predictable workflow timing

  • Accurate handling of +0, +1, +2, and higher values

  • Correct behavior for weekend triggers


You do not need to change anything unless you were intentionally depending on the old behavior, which is unlikely. Everything will continue to function as before, just more reliably.

We hope this update provides accurate scheduling. As always, please feel free to give us your feedback.

Thank you!