The Maximum Consecutive Shifts Alert includes the standard Alert configuration:
The Severity and Suppressible attributes are further described here.
The next part of the configuration defines what is characterised as "consecutive time".
You can define a time period using the "Start-Finish" or by selecting one or more Shift Definitions in the "Criteria" list (not both). This specifies the time periods that are checked as being "consecutive". The "Max Consecutive Shifts" declares how many of the time period are allowed to run on consecutive days before a beak is required. The "First Day Off Duration" indicates how many hours are considered as the "first" day off. For normal operations this can be set to "24:00" but where night/day shift transitions occur, "36:00" might be appropriate to ensure that the workers get at least one full daylight period off. For normal operations, the "Applicable Shifts" can remain as "Standard Only". Other values are used when dynamic Availability Rostering is enabled.
The configuration so far causes the alert to check for ANY on-duty time at all after the break to test the break duration, e.g. Overtime, other Shifts, Training etc. However, you can specify a set of Shifts that are checked after the break in the "Post Shifts" list. If the list has items and time occurs that is NOT in the list then it is ignored and the break calculation is not interrupted.
All the above assumes that the break that is required is AFTER the run of consecutive shifts. However, you can also define a break that needs to be checked BEFORE the consecutive run. By selecting "Pre Shifts" instead of "Post Shifts", the break duration and those shifts in the "Pre Shifts" list (the label will change) are checked BEFORE the consecutive run. Regardless, the consecutive run is always defined by either the "Start-Finish" value or the Shifts listed as the "Criteria".