Daily provider-status observations and published incident history for InnFlow.
Component incident
InnFlow has an active component incident; no global outage is indicated. Verified .
Official provider source.
Looking for an update now? Check the current status, or follow InnFlow for future changes.
64.9%of 37 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
56.7%
30
13
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 2Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
September 2026
HotelKey Daily Activity Imports Returning Values of Zero
We're continuing to work with our partners at HotelKey on the issue causing some Daily Activity imports to contain values of "0."
In the meantime, our team has identified a change on the Inn-Flow side that will increase the speed at which we process the corrected file from HotelKey upon receipt, and we are actively working on that. In the meantime, our team is monitoring affected imports and re-running them as updated files are received. Imports for affected properties have been caught up through today, Friday, September 25.
We will continue running these imports daily and will share specific guidance if any action is needed on your part. If you have any additional questions, please contact our Support team at support@inn-flow.com.
identified
We've identified an issue with data being sent from HotelKey's system to Inn-Flow, for some HotelKey properties. For affected imports, Inn-Flow is receiving Daily Activity data that contains values of "0". Because the data itself is received successfully, the import may show as completed in Inn-Flow even though the values are all zero. This issue does not affect all HotelKey properties.
Inn-Flow's systems are receiving and processing data as expected. We're working closely with our partners at HotelKey, who are reviewing the data being sent to Inn-Flow, to understand the cause for all zeros to be sent, and to reach a resolution as quickly as possible. Once the issue is resolved, Inn-Flow will re-run the import and provide any additional guidance for updating Daily Activity.
If you have questions, please contact our Support team at support@inn-flow.com.
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/...
identified
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...
identified
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...
identified
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...
monitoring
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.
identified
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...
Legacy Incident Archive
15 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
April 2026
Degraded Performance
minorSource not attested
Last archived state: resolved
View archived record details
identified
We are currently experiencing degraded performance across the InnFlow platform, including server errors and slower load times. This is related to an active incident with an upstream cloud service provider that is impacting multiple platforms beyond InnFlow.
investigating
Users are reporting degraded performance across the platform. Our engineers are investigating the cause.
Degraded Performance
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
Users are reporting degraded performance across the platform. Our engineers are investigating the cause.
Timeclock Error - Employees Unable to Clock In
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
Degraded Performance
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
Users are reporting degraded performance across the platform. Our engineers are investigating the cause.
