Anomaly #26 – Continuous duration not respected
Follow
This occurs when, in a presence model with the “clock-in and clock-out” stamping type, there is a “Presence” band with flexible hours where the “Continuous duration” flag is enabled (see image), and there are interruptions between the bands resulting from the day’s attendance processing.
Note: The Continuous duration flag is useful only when bands have a wide range for “Accepted start time from/to” and “Accepted end time from/to”. Typically, for narrow ranges, the anomaly raised is:
#8 – The number of worked hours is sufficient but not aligned with the expected time bands
Issue: During the processing of a day’s timestamps, for the bands described above, the period within which no interruptions must occur is calculated from the start of the first band associated with a reason that does not exclude company working hours and is not of the “missing hours” type, up to the earliest of:
- its maximum duration defined in the presence model, if any;
- the time indicated in the band’s “Accepted end time to” field, if any;
- the model’s Maximum working day duration, if set.
In the list of bands for that day, the two bands between which the interruption occurs will be highlighted in red.
Resolution: the employee can submit one or more timestamp requests or an absence request (e.g., leave, vacation, etc.) to cover the affected period.
In addition to the above, HR Managers or any Admin users can directly add new timestamps or edit existing ones, then click “Process timestamps” again.
Comments
0 comments
Please sign in to leave a comment.