Manage flag settings
Configure flags in your MobiClocks system.
Use the flag management settings to control which flag types MobiClocks applies to timelogs. This gives you the flexibility to enable only the flags relevant to your organization's time tracking policies as well as adjust flag types accordingly.
Flags checklist
To manage flag settings, go to Administration () > Flag management. The flag checklist provides a complete overview of all the flags available in the system. Each flag includes:
- Flag name: The name of the flag
- Description: Brief explanation of when the flag is applied
- Type: The specific flag type identifier. The following types are available:
- Critical: These flags cannot be disabled and are automatically resolved when the underlying issue is fixed. They block timelog approval, cost coding, and payroll approval until resolved.
- Advisory: These flags can be manually resolved and don't block workflows. Also, these can be recategorized as Critical or Informational based on your needs.
- Informational: These flags provide context without blocking workflows and can be recategorized as Critical or Advisory if needed.
- Status: Select to enable the flag type, or clear to disable it. When a flag is unchecked, it's no longer available in timelog flags and won't be applied to new timelogs.
The next section provides a full list of all the flags, describing each one and the cases when it is applied.
Flags reference
Flag name | Description | Type | Status |
---|---|---|---|
Missed Punch | The flag is applied automatically to hourly employees in the following cases:
Under Administration () > Settings > Punch and Timelogs > Salary Punch Policy, you can choose if the missed punch flag is applicable to salary employees the same way as it's applicable to hourly employees. | Critical (cannot be edited) | Cannot be edited |
Time Overlap | The flag is applied when multiple timelog entries exist for the same employee on the same day during overlapping periods. This usually occurs when an employee manually logs time while an offline punch syncs for the same timeframe. | Critical (cannot be edited) | Cannot be edited |
Unfinished meal break | The flag is applied if trackable meal policy is activated, and the employee hasn't ended the meal before punching out. | Critical (cannot be edited) | Cannot be edited |
Face Spoofing | The flag is applied If the face liveness level during punch is lower than the percentage set in Administration () > Settings > Punch and Timelogs > Face Liveness Check. | Advisory (can be edited) | Can be edited |
Late meal break | The flag is applied if trackable meal policy is activated, and the employee hasn't taken a break during the specified period. | Advisory (can be edited) | Can be edited |
Manually Updated | The flag is applied when an existing punch made from Personal App or Kiosk App has been manually modified later on. | Advisory (can be edited) | Can be edited |
Missed meal break | The flag is applied if trackable meal policy is activated, and the employee hasn't taken a break during the day. | Advisory (can be edited) | Can be edited |
Out of geofence | The flag is applied if the job site has a geofence zone set, and the employee punches out (punching in beyond the geofence zone is disabled in this case) beyond the geofence zone. | Advisory (can be edited) | Can be edited |
Out of working hours | The flag is applied if the employee has made a punch outside of job site's working hours, which is specified in the Working Hours Policy section of job site settings. | Advisory (can be edited) | Can be edited |
Pin Punch | A pin punch is applied in the following cases:
| Advisory (can be edited) | Can be edited |
Short meal break | The flag is applied if trackable meal policy is activated, and the employee's break duration is shorter than the specified break period. | Advisory (can be edited) | Can be edited |
Time Spoofing | The flag is activated if the difference between the employee's device time and the MobicCocks system time is more than 5 minutes. This way, the system detects the cases when the device time has been changed before the punch. | Advisory (can be edited) | Can be edited |
Attempt Failed | This flag is applied when one of the punch attempts has failed but the last attempt is successful. If 3 attempts in a row fail, the case falls under Pin Punch. | Informational (can be edited) | Can be edited |
Different Job Site | The flag is applied when the employee's punch job site is different from the assigned job sites. Note: The flag is not applied if the Roaming employee setting is on for the employee. Also, if the job site is then manually changed to the employee's assigned job site, the flag is not removed automatically and needs to be resolved manually. | Informational (can be edited) | Can be edited |
Different org unit | The flag is applied if the employee has punched at a job site that doesn't belong to their organization unit. | Informational (can be edited) | Can be edited |
Offline Punch | If the employee's device is offline during the punch, the punch is flagged as an offline punch. The punch is recorded in the system as soon as there is a network connection. | Informational (can be edited) | Can be edited |
Clear old flags
Use the Clear flags setting to remove all flags from timelogs older than a specified date. This helps maintain clean historical data while focusing on current issues.
To clear old flags:
- In the flag settings page, locate the Clear flags section.
- Set the date before which all flags should be cleared.
- Select Clear Flags to remove flags from older timelogs.
Updated about 14 hours ago