Historique des pannes de Injixo

1. 30 juillet 2026 à 09:29 UTCinvestigating

   Dans certains cas, le module d'adhésion intrajournalier pourrait manquer d'états ou de statistiques corrects. Nous enquêtons sur la question.

2. 30 juillet 2026 à 12:37 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats. Une fois confirmé, nous déclencherons le rapprochement des données.

3. 31 juillet 2026 à 06:55 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 17 juillet 2026 à 07:40 UTCresolved

   En raison d'un problème de politique de réseau sous-jacent, certains utilisateurs auraient pu subir une panne partielle du système de 8h51 à 8h58 (GMT+2).

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 27 mai 2026 à 10:50 UTCinvestigating

   Some customers experience Adherence statuses not being correct. We are investigating the issue.

2. 27 mai 2026 à 11:12 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 27 mai 2026 à 11:13 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 27 mai 2026 à 11:21 UTCmonitoring

   The fix seems to work, we see decreased refresh times. We are backfilling the historical adherence status.

5. 27 mai 2026 à 12:44 UTCresolved

   This incident has been resolved.

1. 18 mai 2026 à 07:11 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 19 mai 2026 à 07:32 UTCresolved

   This incident has been resolved.

1. 13 mars 2026 à 14:39 UTCidentified

   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.

2. 13 mars 2026 à 20:48 UTCresolved

   This incident has been resolved.

1. 13 mars 2026 à 14:36 UTCresolved

   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.

1. 12 mars 2026 à 11:31 UTCinvestigating

   We are currently investigating this issue.

2. 12 mars 2026 à 13:28 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 12 mars 2026 à 16:52 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 12 mars 2026 à 19:53 UTCresolved

   This incident has been resolved.

1. 24 février 2026 à 08:09 UTCinvestigating

   We are currently investigating this issue.

2. 24 février 2026 à 08:37 UTCresolved

   This incident has been resolved.

1. 9 janvier 2026 à 11:48 UTCinvestigating

   Currently, login via SSO is not possible. The login via user name and password still works as expected. We're investigating the situation.

2. 9 janvier 2026 à 12:03 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 9 janvier 2026 à 15:03 UTCresolved

   This incident has been resolved.

1. 8 décembre 2025 à 10:25 UTCinvestigating

   This morning, we have received reports about optimization process failing for some customers. The problem is under investigation.

2. 8 décembre 2025 à 15:58 UTCmonitoring

   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.

3. 9 décembre 2025 à 08:25 UTCresolved

   This incident has been resolved.

1. 24 octobre 2025 à 06:49 UTCinvestigating

   We are currently investigating this issue.

2. 24 octobre 2025 à 06:53 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 24 octobre 2025 à 09:15 UTCresolved

   This incident has been resolved.

1. 8 octobre 2025 à 13:32 UTCresolved

   Fixed at 13:58. Peopleware not available (Error 500 in Plan > Schedules and Time off).

1. 18 septembre 2025 à 12:25 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 18 septembre 2025 à 13:22 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 18 septembre 2025 à 15:35 UTCresolved

   This incident has been resolved.

1. 31 juillet 2025 à 14:25 UTCinvestigating

   Our public API documentation is currently not available. We are investigating the issue.

2. 1 août 2025 à 08:56 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 1 août 2025 à 09:48 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 1 août 2025 à 12:45 UTCresolved

   This incident has been resolved.

1. 18 juin 2025 à 21:56 UTCinvestigating

   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.

2. 20 juin 2025 à 08:14 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 20 juin 2025 à 11:31 UTCresolved

   This incident has been resolved, we are working on backfilling the data that might have been wrongly imported during the outage.

1. 28 avril 2025 à 09:19 UTCinvestigating

   We are currently investigating this issue.

2. 28 avril 2025 à 09:40 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 28 avril 2025 à 09:40 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 28 avril 2025 à 09:58 UTCresolved

   This incident has been resolved.

1. 1 avril 2025 à 09:49 UTCinvestigating

   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.

2. 2 avril 2025 à 15:18 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 4 avril 2025 à 06:09 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 7 avril 2025 à 11:29 UTCresolved

   This incident has been resolved.

1. 6 mars 2025 à 08:49 UTCidentified

   We received reports about an error message when users try to connect to Shift Center.

2. 6 mars 2025 à 08:56 UTCmonitoring

   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.

3. 6 mars 2025 à 10:17 UTCresolved

   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.

1. 22 novembre 2024 à 09:52 UTCinvestigating

   Users receive error with login attempt to injixo services. Our engineers are working to resolve the problem, apologies for the inconvenience.

2. 22 novembre 2024 à 09:55 UTCresolved

   This incident has been resolved.

1. 1 octobre 2024 à 12:01 UTCinvestigating

   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.

2. 1 octobre 2024 à 12:02 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 1 octobre 2024 à 13:31 UTCmonitoring

   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

4. 1 octobre 2024 à 16:13 UTCresolved

   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.