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 be pending approval.
Frozen Punches Error Messages
insufficient-permission-to-report-this-entry
* When a punch is manually entered on the timesheet by the employee but the employee does not have permissions
"Entry was rejected because the employee does not have access to create this entry"
entry-rejected-after-approval
* When the timesheet was approved and an entry was added to the timesheet
"Entry was rejected because the timesheet was already approved"
missing-compensation-information
*When employee is missing required compensation details
"Entry was rejected because the employee is missing compensation information."
entry-invalid-for-timesheet
* When the punch is outside of the limits (start & end) of the pay period
"Entry was rejected because it is outside of the pay period: [pay period start - end date]"
inactive-employee
*When the employee is inactive and a new punch is saved
"Entry was rejected because the employee is inactive"
entry-duplicated
* When the entry is duplicated within the same request (Security Check)
"Entry was rejected because this entry is a duplicate"
reached-overtime
*When the overtime restriction is set and the employee tries to clock in when they already have overtime
"Entry was rejected because the overtime restriction limits were reached"
restricted-by-worked-hours
*When the worked hours restriction is set and the employee tries to clock in when they have reached the threshold
"Entry was rejected because the worked hours restriction limits were reached"
employee-is-not-user
* When the user who created the entry is not a system user. The entry has an employee ID but the user identity is not found within the system (Security Check)
"Entry was rejected because the employee's identity was not found"
access-not-allowed
* When the punch origin is TC, Web, Mobile, etc and the employee does not have have access to use
"Entry was rejected because the employee did not have access to the [origin]"
multiple-origin-detected
* When the entry has multiple origins (time clock, web, mobile, etc)
"Entry was rejected because the entry has multiple origins"
multiple-employees-punches
* When an employee creates a bulk of entry and the entries have multiple employees 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
* When web restriction by IP is set and the punch is sent with an IP address that is not allowed
"Entry was rejected because the entry was made from an unauthorized IP address"
missing-mobile-identifier
* When the punch is made from an unknown IMEI or ID
"Entry was rejected because the entry was missing the IMEI or ID"
multiple-mobile-identifier-not-allowed
* When the punch is sent with multiple IMEI or ID that are not allowed
"Entry was rejected because of an unauthorized IMEI or ID"
mobile-not-allowed
* When mobile restriction by IMEI or ID is set and the punch is sent with an IMEI or ID not allowed
"Entry was rejected because the entry was made from an unauthorized IMEI or ID"
missing-photo-identifier
* When the photo required is set and the punch is sent without a photo
"Entry was rejected because the entry was missing the photo"
missing-punch-geo-position
* When the punch does not have the geolocations details
"Entry was rejected because the entry was missing the geolocation details"
punch-out-of-fence
* When enforce geofence is set and the punch is made out side of the Geofence
"Entry was rejected because the entry was made outside of the Geofence"
invalid-timesheet-for-employee-punch
* When the punch is sent to a timesheet that did 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
* When punch restrictions is set and the employee punches outside of the thresholds
"Entry was rejected because the entry was outside of the punch restriction parameters"