The Automatic resolution of anomalies extension allows companies to automatically resolve unexpected presence and unjustified absence anomalies. It applies extra work or absence justifications without requiring manual intervention.

Once you activate the extension, you need to configure at least one correction rule for the feature to work. These rules tell Fluida how to handle anomalies automatically. You can choose whether to apply them to the entire company or to specific people, and define which justification to use.

After a rule is set up, anomalies are automatically justified based on your settings. For example, if your company uses the time bank feature, you can decide that all unexpected absences are automatically justified as "Time Bank Usage" and all extra hours as "Time Bank Accumulation." This will also automatically update everyone's time bank balance.

Fluida provides two default rules for automatic anomaly resolution:

By default, these rules are disabled. An Administrator or Power User can enable them (and modify their parameters if needed). To do this:

The rule is now enabled and will apply to the attendance calendars of the chosen users starting the next day.

💡 Example: You create a rule that automatically applies a "Time Bank Usage" justification for absences up to 60 minutes. Starting the day after activation, if an employee has an unexcused absence of 45 minutes, the anomaly will automatically turn into 45 minutes of "Time Bank Usage", applying any rounding rules set for that justification.

If the default rules don't meet your company's needs, or if you need to create additional rules for specific people or teams, you can add custom rules. To do this:

The custom rule is now created and will apply to the selected users' attendance calendars starting the next day.

💡 Example: You create a custom rule for Extra Work that automatically applies "Time Bank Accumulation" for anomalies up to 60 minutes. Starting the following day, if an employee works 45 extra minutes, Fluida will automatically convert that anomaly into 45 minutes of "Time Bank Accumulation", following the justification's rounding rules.

When creating a rule, Fluida automatically checks if another rule of the same category (e.g., two rules for Extra Work or two for Absences) already applies to the same people. If there is an overlap, a conflict is flagged, and you will be asked which rule to keep active before saving.

To prevent two rules from trying to resolve the same anomaly in different ways, Fluida checks the combination of the rule category and the assigned users.

If a rule of the same category already exists for the same people, the new rule conflicts with the existing one—even if the justification or maximum duration is different. Fluida will prompt you to choose which rule to keep active.

However, a company-wide rule and a rule assigned only to specific people can coexist, even if they belong to the same category. When a user falls under both, Fluida always applies the more specific rule (the one directly assigned to that person).

Example

You have a company-wide rule for Absences that applies "Paid Leave". If you try to create another company-wide rule for Absences that applies "Time Bank Usage", Fluida will flag a conflict because both rules apply to the entire company for the same anomaly category.

However, if you create an Absence rule assigned only to a specific person—say, Julia—that rule can coexist with the company-wide rule. Fluida will apply the specific rule to Julia, while the company-wide rule will still apply to everyone else.

Automatic anomaly resolution rules only apply starting the day after they are created. Therefore, a new rule cannot be applied retroactively to days that have already been processed.

To force the rule on a past date, you can make a minor edit to that day (for example, open an existing clock-in and save it without changing any details). This prompts Fluida to recalculate the day, rerun the reconciliation, and automatically apply the rule if the conditions are met.

If you created a rule but don't see the justification applied, first verify that attendance reconciliation is active for your company. If reconciliation is turned off, Fluida won't generate anomalies, meaning it can't resolve them.

Next, make sure the user has properly configured attendance rules assigned to them. Automatic resolution rules only handle anomalies generated by the reconciliation process. If your attendance rules don't trigger the expected anomaly, there will be nothing for the system to resolve.

Example

An employee's attendance rule is set up so that extra work is only flagged if it reaches at least 60 minutes. If you create an automatic resolution rule for that employee to cover Extra Work up to 30 minutes with "Time Bank Accumulation", 30 extra minutes of work will never be automatically converted. Since it doesn't reach the minimum threshold set in the attendance rule, Fluida never triggers an extra work anomaly in the first place.