The Automatic resolution of anomalies feature automatically fixes unexpected presence and unjustified absence anomalies. It applies a justification based on rules defined by your company.
It is designed to handle recurring or highly predictable scenarios. This reduces manual tasks for Administrators and Power Users, leaving only specific cases that require personal review for manual handling.
This guide covers the required prerequisites, when automatic corrections occur, how to identify an automatically applied justification, and when manual intervention may still be needed.
Prerequisites
For automatic anomaly resolution to work, all of the following conditions must be met:
Attendance Management and Smart Clocking are active for your company.
The Automatic Anomaly Correction extension is enabled.
The person in question falls under an active correction rule (the rule applies either company-wide or to specific users, including them).
If even one of these prerequisites is missing, automatic resolution will not run.
When does automatic anomaly resolution happen?
With automatic resolution enabled, Fluida doesn't wait for the midnight reconciliation (the process that compares clock-ins against the scheduled shift). Instead, every time a clock-in is registered, the system performs an immediate reconciliation. If it detects an anomaly that matches a configured rule, it applies the justification automatically—provided there isn't already another justification from the same category on that day.
How to identify an automatically applied justification
You can spot a justification assigned via automatic resolution by clicking on it. The details will display the note "Applied by Divinator".
This tag makes it easy to tell automatically assigned justifications apart from those requested by employees or added by managers.
Additionally, an automatically applied justification:
Does not trigger notifications.
Will not be reapplied by the system if you manually edit or delete it.
What to do if an automatically applied justification is incorrect
While automatic resolution handles recurring tasks, it never prevents human intervention when needed.
If an automatically applied justification isn't right—perhaps a rule parameter needs tweaking or it is simply a one-off exception—you can always step in to edit or delete it. Once you do, Divinator will not overwrite your manual change or attempt to apply the automatic justification again.
Furthermore, having a manual justification in place doesn't block the entire rule. If the remaining anomaly (the part not yet covered by the existing justification) still fits the rule's criteria regarding type, time limit, and user scope, Fluida will automatically apply the justification to that leftover portion.
Example
An employee scheduled to work 9:00 AM–6:00 PM requests and receives approval for a 2-hour paid leave (from 4:00 PM to 6:00 PM). However, they clock out early at 3:00 PM. The total absence anomaly is 3 hours, but 2 hours are already covered by the approved leave. If an automatic correction rule applies to this scenario, Fluida will automatically add the justification only for the remaining hour (3:00 PM to 4:00 PM), leaving the existing leave untouched.
When automatic anomaly resolution does not work
Automatic anomaly resolution will not trigger if any of the necessary conditions are missing:
No matching rule exists, or the rule doesn't apply to that specific person.
The justification linked to the rule was disabled or deleted. Fluida will not look for an alternative justification; the rule will have no effect until it is updated with a valid justification.
Clock-ins are missing or incomplete. Automatic resolution triggers when a clock-in is registered, as that is when Fluida checks if the anomaly matches a rule. If an employee doesn't clock in at all, or clocks in but forgets to clock out, the anomaly is only caught during the midnight reconciliation and will not be corrected automatically. In these cases, you must resolve the anomaly manually.
Frequently asked questions
What happens if the anomaly exceeds the maximum duration set by the rule?
When configuring a rule, you set a maximum duration limit for Fluida to resolve (the Up to field). If the actual anomaly exceeds this limit, Fluida still applies the justification, but only up to the maximum value specified in the rule. The remaining time will stay flagged as an anomaly for manual review.
Example
A rule automatically applies an Overtime justification for extra work anomalies up to 60 minutes. An employee works 90 extra minutes. Fluida will automatically apply 60 minutes of Overtime, while the remaining 30 minutes will stay flagged as an anomaly for manual check and intervention.
Currently, it is not possible to prevent the automatic application if the anomaly exceeds the maximum duration set by the rule.
If I edit or add a clock-in on a past date, will the rule apply?
Yes. Even though new rules only apply going forward (starting the day after creation), editing a past date by adding a forgotten clock-in or modifying an existing one prompts Fluida to re-run the reconciliation. If the conditions are met, the rule will apply to that past date.