This time expression design will help avoid some of the congestion that can occur when Flux needs to process a business interval over a very large date range on a trigger, and ensures that the engine can process your workflows much more quickly.
Business Interval Intersections
When intersecting two Business Intervals using the API, you may find that holidays that are defined in both calendars are no longer recognized in the resulting intersection. If this occurs, check to make sure that the intersected calendars utilize matching time zones – if the time zones for the holidays in the two original calendars do not match, portions of the holidays will not overlap, causing some of the day to be included in the resulting intersection.
For example, consider two calendars: New York Holidays and Chicago Holidays. In New York, the New Year's Day holiday would begin on:
Jan 1 00:00:00 Eastern Standard Time
In Chicago, New Year's Day would begin on:
Jan 1 00:00:00 Central Standard Time
At first glance, it might appear that these holidays are equivalent; however, when the intervals are intersected, one hour of the day will actually be included on Jan 1.
This occurs because the time period from 00:00:00 to 01:00:00 is excluded from our New York Holidays calendar – in Chicago, though, this would be 23:00:00 to 00:00:00, Dec 31, a time period we haven't excluded in that calendar. Since the interval can only contain excludes defined in both calendars, this one-hour period will be included in the resulting intersection.
Be sure to take this into account when planning for business calendar intersections across time zones!