Timeclock: Errors When Saving or Loading Time Entries

Update: September 4, 2026, 2:04 PM EDT: Microsoft has marked the Azure Cognitive Services issue as resolved. Employees should be able to punch in and out via facial recognition normally. If you encounter an error, please retry, and let us know if it persists. We'll post a final confirmation once we're confident the fix is holding.

Catching up missed punches: Any punches missed during the outage can be corrected. Full instructions here: https://support.inn-flow.net/support/solutions/articles/...

Update: September 4, 2026, 3:14 PM EDT: We do not yet have a resolution to report. Microsoft Azure is still working to restore the Cognitive Services outage affecting facial recognition in Time Clock, and we have not received an estimated resolution time from them.

Workarounds: Our support team has documented all of the alternate ways to punch employees in and out if your team is experiencing errors from this event: https://support.inn-flow.net/support/solutions/articles/1000336416

We are g...

Update: September 4, 2026, 11:22 AM EDT: The Microsoft Azure issue affecting facial recognition on Time Clock is still ongoing. Azure has not yet restored full service, and we continue to see intermittent failures.

What's affected: Facial recognition sign-in at Time Clock only.

Workarounds available now: https://support.inn-flow.net/a/solutions/articles/1000336416

Retrying facial recognition will also often succeed, as failures are intermittent.

Coming shortly: Our support team is workin...

Update: We are again seeing failures with Microsoft Azure Cognitive Services, the platform that powers facial recognition on our Time Clocks. Azure has confirmed the resource is unavailable and is working to recover it.

What's affected: Facial recognition sign-in for Time Clock.

What you may see: Employees attempting to clock in or out via facial recognition may encounter errors such as "Operation returned an invalid status code 'Conflict'" or "'Internal Server Error'." Attempts are current...

Update: Microsoft Azure has resolved the underlying service issue and Timeclock should now be functioning normally. If you were previously seeing errors such as "Operation returned an invalid status code 'Conflict'" or "'Internal Server Error'," please try again. Our team is continuing to monitor to confirm full recovery.

We are aware that some customers are receiving error messages in Timeclock, including "Operation returned an invalid status code 'Conflict'" and "Operation returned an invalid status code 'Internal Server Error'."
We have identified the cause as an ongoing service outage with Microsoft Azure, our cloud hosting provider. This is affecting Timeclock functionality for multiple customers.
Our team is actively monitoring Azure's remediation efforts and will provide an update as soon as we have mor...