Business Calendars

A holiday calendar tells a workflow which days your team does not work, beyond the weekend. Once a workflow has one, every date it works out, run due dates, step due dates, reminders and recurring starts, treats those holidays the same way it treats a Saturday.

Holiday calendars are enabled per account. If you do not see Holiday Calendars under Settings, contact support and we will turn them on.

There are two separate ideas here, and the article covers both:

• Landing. A date that lands on a weekend or holiday is moved to the next or previous business day. This is set per workflow and per recurring schedule.
• Counting. "Due in 2 days" can mean 2 business days, so the count steps over weekends and holidays. This is chosen per step.

Create a holiday calendar

1. Go to Settings and open Holiday Calendars.
2. Click Add Calendar and name it.
3. Choose a regional template if one fits: US Federal Holidays, UK Bank Holidays (England and Wales), Canada Statutory Holidays (Ontario) or Australia Public Holidays (New South Wales). The observed dates fill in for the coming years.
4. Add, edit or remove dates by clicking a day. Imported dates and hand-added dates are shown in different colours so you can tell them apart.

Calendars belong to the account, so one calendar can serve many workflows. A calendar built from a template keeps itself topped up about five years ahead, so it does not quietly run out of dates.

Attach it to a workflow

1. Open the workflow in the editor and click Settings.
2. Under Timing, check the Business Days your team works.
3. Pick the calendar under Holiday Calendar.
4. Under Due Dates on Non-Business Days, choose what happens when a calculated date lands on a weekend or holiday: keep the calculated date, move to the next business day, or move to the previous business day.
5. Click Update.

From then on the rule applies to run due dates, step due dates and reminders on new runs, and on runs you update from the workflow.

Recurring runs that land on a holiday

A recurring schedule has its own landing rule, set when you create or edit the schedule under If a run lands on a non-business day or holiday:

• Start on the scheduled day
• Start on the next business day
• Start on the previous business day
• Skip that run (do not start it)

With a move rule, a run that would have started on a holiday is created on the next or previous business day instead, and the run's activity records the move and names the holiday. With skip, that occurrence is dropped and the schedule carries on from the next one; the schedule list describes it as "not started if it lands on a non-business day or holiday". Skip is a scheduling choice only. A due date cannot be skipped; it is always moved.

Counting due dates in business days

A step due "N days" after the run starts can count calendar days or business days. Choose it in the step's due date settings: next to the number and unit, pick Business days or Calendar days. The same choice exists for the workflow's expected duration.

With business days, the count steps over weekends and the calendar's holidays. A run started on Thursday, July 2, with a holiday on Friday, July 3, puts a one-business-day step on Monday, July 6, a two-business-day step on Tuesday, July 7, and a three-business-day step on Wednesday, July 8. If a counted date still lands on a non-business day, the workflow's landing rule then moves it.

Notes

Days are classified in the time zone of the workflow's department. A team spread across time zones should check which department owns a workflow before relying on a date near midnight.

Related articles

• Configuring Business Days
• Schedule a workflow run to recur every day, week, month
• Set Due Dates on Steps
• Understanding workflow expected duration