clocking_outside_employment_period
The clocking instant falls before the employee's hire date or after their termination date, so nothing was written to the time record. Both the hire day and the termination day accept clockings. Approving a correction checks the current employment period again, and a rejected approval leaves the request pending.
| Code | Type | HTTP | Category |
|---|---|---|---|
clocking_outside_employment_period | invalid_request_error | 422 | Time Tracking |
Cause
The clocking instant falls before the employee's hire date or after their termination date, so nothing was written to the time record. Both the hire day and the termination day accept clockings. Approving a correction checks the current employment period again, and a rejected approval leaves the request pending.
What to do
Check the date sent in occurred_at (or the start and end of the manual entry or of the correction) against the employee's hire and termination dates, and send a date inside that period or fix the employee's hire date first with PUT /v1/employees/{employee}. Clocking out, pausing or resuming a span that is already open is never rejected by this rule.