Punches that have been blocked from an employee's timesheet due to specific restrictions are called frozen punches.
Recovering Frozen Punches from the Dashboard
On the Dashboard, click Exceptions or the Frozen Punches widget.
Locate the employee with Frozen Punches and select the checkbox next to their name.
Click Recover.
Confirm by clicking Yes, Recover.
Recovering Frozen Punches from the employee’s Timesheet
Go to the employee's Timesheet and click on the employee's name.
Click the snowflake icon.
Select the checkbox for all Frozen Punches.
Click Recover.
Confirm by clicking Yes, Recover.
Once recovered, a message will display saying Punches Recovered. Click OK to proceed.
The recovered punches will now be pending approval.
Frozen Punches Error Messages
insufficient-permission-to-report-this-entry
Triggered when an employee manually enters a punch on their timesheet but lacks the required permissions.
"Entry was rejected because the employee does not have access to create this entry."
entry-rejected-after-approval
Triggered when a punch is added after the timesheet has already been approved.
"Entry was rejected because the timesheet was already approved."
missing-compensation-information
Triggered when the employee is missing required compensation details in their profile.
"Entry was rejected because the employee is missing compensation information."
entry-invalid-for-timesheet
Triggered when the punch falls outside of the pay period's start or end dates.
"Entry was rejected because it is outside of the pay period: [pay period start - end date]."
inactive-employee
Triggered when a punch is recorded for an inactive employee.
"Entry was rejected because the employee is inactive."
entry-duplicated
Triggered when a duplicate punch is submitted in the same request (security check).
"Entry was rejected because this entry is a duplicate."
reached-overtime
Triggered when an employee tries to punch in after reaching the set overtime limit.
"Entry was rejected because the overtime restriction limits were reached."
restricted-by-worked-hours
Triggered when an employee tries to punch in after exceeding the worked hours threshold.
"Entry was rejected because the worked hours restriction limits were reached."
employee-is-not-user
Triggered when the system cannot verify the identity of the user who submitted the punch (security check).
"Entry was rejected because the employee's identity was not found."
access-not-allowed
Triggered when the punch originates from a source (e.g., web, mobile, clock) the employee does not have access to use.
"Entry was rejected because the employee did not have access to the [origin]."
multiple-origin-detected
Triggered when a punch includes multiple origin sources (e.g., clock and mobile).
"Entry was rejected because the entry has multiple origins."
multiple-employees-punches
Triggered when a bulk punch request includes multiple employee IDs (security check).
"Entry was rejected because the employee who created the entry does not match the employee ID attached to the entry."
ip-not-allowed
Triggered when a punch is made from a web IP address not authorized by the restriction settings.
"Entry was rejected because the entry was made from an unauthorized IP address."
missing-mobile-identifier
Triggered when a mobile punch is submitted without an IMEI or device ID.
"Entry was rejected because the entry was missing the IMEI or ID."
multiple-mobile-identifier-not-allowed
Triggered when a punch includes multiple or unauthorized device IDs.
"Entry was rejected because of an unauthorized IMEI or ID."
mobile-not-allowed
Triggered when a punch is made from a mobile device that is not on the allowed list.
"Entry was rejected because the entry was made from an unauthorized IMEI or ID."
missing-photo-identifier
Triggered when photo capture is required and the punch is submitted without a photo.
"Entry was rejected because the entry was missing the photo."
missing-punch-geo-position
Triggered when the punch does not include geolocation details.
"Entry was rejected because the entry was missing the geolocation details."
punch-out-of-fence
Triggered when a geofence is enforced and the punch is submitted from outside the allowed area.
"Entry was rejected because the entry was made outside of the Geofence."
invalid-timesheet-for-employee-punch
Triggered when a punch is submitted to a timesheet that does not belong to the employee.
"Entry was rejected because the entry was allocated to a timesheet that is not related to the employee."
missing-schedule-for-restriction
Triggered when punch restrictions are in place and the punch violates the defined schedule thresholds.
"Entry was rejected because the entry was outside of the punch restriction parameters."