Injixo 장애 기록

1. 2026년 7월 30일 오전 9:29 UTCinvestigating

   어떤 경우에는 Intraday 부착 모듈은 올바른 상태 또는 통계를 누락할 수 있습니다. 우리는 문제를 조사하고 있습니다.

2. 2026년 7월 30일 오후 12:37 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다. 일단 확인되면, 우리는 데이터의 재구성을 트리거합니다.

3. 2026년 7월 31일 오전 6:55 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 17일 오전 7:40 UTCresolved

   네트워크 정책 문제로 인해 일부 사용자는 8 : 51 AM에서 8 : 58 AM (GMT + 2)의 부분 시스템 정전을 경험할 수 있습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 5월 27일 오전 10:50 UTCinvestigating

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

2. 2026년 5월 27일 오전 11:12 UTCidentified

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

3. 2026년 5월 27일 오전 11:13 UTCmonitoring

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

4. 2026년 5월 27일 오전 11:21 UTCmonitoring

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

5. 2026년 5월 27일 오후 12:44 UTCresolved

   This incident has been resolved.

1. 2026년 5월 18일 오전 7:11 UTCidentified

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

2. 2026년 5월 19일 오전 7:32 UTCresolved

   This incident has been resolved.

1. 2026년 3월 13일 오후 2: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. 2026년 3월 13일 오후 8:48 UTCresolved

   This incident has been resolved.

1. 2026년 3월 13일 오후 2: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. 2026년 3월 12일 오전 11:31 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 3월 12일 오후 1:28 UTCidentified

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

3. 2026년 3월 12일 오후 4:52 UTCmonitoring

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

4. 2026년 3월 12일 오후 7:53 UTCresolved

   This incident has been resolved.

1. 2026년 2월 24일 오전 8:09 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 2월 24일 오전 8:37 UTCresolved

   This incident has been resolved.

1. 2026년 1월 9일 오전 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. 2026년 1월 9일 오후 12:03 UTCmonitoring

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

3. 2026년 1월 9일 오후 3:03 UTCresolved

   This incident has been resolved.

1. 2025년 12월 8일 오전 10:25 UTCinvestigating

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

2. 2025년 12월 8일 오후 3: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. 2025년 12월 9일 오전 8:25 UTCresolved

   This incident has been resolved.

1. 2025년 10월 24일 오전 6:49 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 10월 24일 오전 6:53 UTCmonitoring

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

3. 2025년 10월 24일 오전 9:15 UTCresolved

   This incident has been resolved.

1. 2025년 10월 8일 오후 1:32 UTCresolved

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

1. 2025년 9월 18일 오후 12:25 UTCidentified

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

2. 2025년 9월 18일 오후 1:22 UTCmonitoring

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

3. 2025년 9월 18일 오후 3:35 UTCresolved

   This incident has been resolved.

1. 2025년 7월 31일 오후 2:25 UTCinvestigating

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

2. 2025년 8월 1일 오전 8:56 UTCidentified

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

3. 2025년 8월 1일 오전 9:48 UTCmonitoring

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

4. 2025년 8월 1일 오후 12:45 UTCresolved

   This incident has been resolved.

1. 2025년 6월 18일 오후 9: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. 2025년 6월 20일 오전 8:14 UTCmonitoring

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

3. 2025년 6월 20일 오전 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. 2025년 4월 28일 오전 9:19 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 4월 28일 오전 9:40 UTCmonitoring

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

3. 2025년 4월 28일 오전 9:40 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2025년 4월 28일 오전 9:58 UTCresolved

   This incident has been resolved.

1. 2025년 4월 1일 오전 9: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. 2025년 4월 2일 오후 3:18 UTCidentified

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

3. 2025년 4월 4일 오전 6:09 UTCmonitoring

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

4. 2025년 4월 7일 오전 11:29 UTCresolved

   This incident has been resolved.

1. 2025년 3월 6일 오전 8:49 UTCidentified

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

2. 2025년 3월 6일 오전 8: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. 2025년 3월 6일 오전 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. 2024년 11월 22일 오전 9:52 UTCinvestigating

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

2. 2024년 11월 22일 오전 9:55 UTCresolved

   This incident has been resolved.

1. 2024년 10월 1일 오후 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. 2024년 10월 1일 오후 12:02 UTCidentified

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

3. 2024년 10월 1일 오후 1: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. 2024년 10월 1일 오후 4: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.