52 Injixo incidents · Juli 2022 — official updates, affected components, duration and resolution details.
In einigen Fällen kann das Intraday-Adhärenzmodul korrekte Status oder Statistiken fehlen. Wir untersuchen das Problem.
Ein Fix wurde implementiert und wir überwachen die Ergebnisse. Einmal bestätigt, werden wir den Datenabgleich auslösen.
Dieser Vorfall wurde behoben.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Aufgrund eines zugrunde liegenden Netzwerkrichtlinienproblems haben einige Benutzer möglicherweise einen Systemausfall von 8:51 Uhr bis 8:58 Uhr (GMT + 2) erlebt.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Some customers experience Adherence statuses not being correct. We are investigating the issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
The fix seems to work, we see decreased refresh times. We are backfilling the historical adherence status.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
There was a problem identified, resulting in agent logouts not being accepted in Shift Center (only). The fix is currently prepared, and since it requires your environment restart, it will be applied automatically during the nearest maintenance window.
This incident has been resolved.
There was a problem identified, resulting in agent logouts not being accepted in Shift Center (only). The fix is currently prepared, and since it requires your environment restart, it will be applied automatically during the nearest maintenance window.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
Currently, login via SSO is not possible. The login via user name and password still works as expected. We're investigating the situation.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
This morning, we have received reports about optimization process failing for some customers. The problem is under investigation.
We have found and fixed the problem. The fix will be deployed at a regular maintenance window. If the fix is needed earlier, please let us know.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Fixed at 13:58. Peopleware not available (Error 500 in Plan > Schedules and Time off).
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Our public API documentation is currently not available. We are investigating the issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We received multiple Tickets about faulty Real-Time Adherence data, especially agents being shown offline, and Intraday data not being updated correctly. We are currently investigating the issues.
A fix has been implemented and we are monitoring the results.
This incident has been resolved, we are working on backfilling the data that might have been wrongly imported during the outage.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
Some customers might experience reduced DB performance and general slowness of the Intraday Adherence page and the /adherence/report API endpoint, leading from long request runtimes up to timeouts. We are currently investigating the issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We received reports about an error message when users try to connect to Shift Center.
A fix is currently implemented. We will need to restart the affected systems, which will cause a short general interruption. After the restart, the Shift Center will be available again.
To fully restore service, we need to restart the affected systems, which will cause a brief general interruption. We expect the Shift Center to be available again within the next hour.
Users receive error with login attempt to injixo services. Our engineers are working to resolve the problem, apologies for the inconvenience.
This incident has been resolved.
We are currently experiencing a problem with adding or editing configuration data in WFM > Administration > Scheduling > Employees (Edge) and when using the search results page after using the search in WFM (Chrome) - In Microsoft Edge, changing employee details does not work under WFM > Administration > Scheduling > Employees. - In other browsers (such as Chrome or Firefox), this does not work on the search results page after using the search field WFM in the upper left corner. The page under WFM > Administration > Scheduling > Employees still works as expected. Workaround for the search in Chrome: Use People and click on the WFM link in the top right after selecting a person. Our team has already identified the root cause and is packaging a fix for deployment that will be available with the next nightly update.
The issue has been identified and a fix is being implemented.
A fix has been implemented. The next scheduled nightly update will automatically fix the problem. For an on-demand update today, contact our support team in a support ticket. The update requires a restart of your injixo instance, which means a short downtime. IE mode in Microsoft Edge may require deleting the Internet Explorer browsing history For information, see "Clear Internet Explorer browsing data using Microsoft Edge" on this page of the Microsoft Support Center: Learn more: https://support.microsoft.com/en-us/microsoft-edge/view-and-delete-browser-history-in-microsoft-edge-00cf7943-a9e1-975a-a33d-ac10ce454ca4
This incident has been resolved. The next scheduled maintenance update will automatically fix the problem. For on-demand updates, contact our support team in a support ticket.