Helloid 장애 기록

1. 2026년 8월 28일 PM 12:27 UTCinvestigating

   우리는 현재 Elastic 보고서에 문제가 있습니다. 예상대로 탄력적인 작품으로 조깅하지만, 보고서는 표시 할 수 없습니다. 우리는 현재 문제를 조사하고 있습니다. API 사용은 영향을받지 않습니다.

2. 2026년 8월 28일 PM 6:13 UTCresolved

   문제는 해결되었습니다. 우리는 모든 것을 안정적으로 유지되도록 상황을 모니터링 할 것입니다.

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

1. 2026년 8월 5일 PM 2:29 UTCinvestigating

   We’re currently experiencing issues with email delivery to the domains @live.nl, @msn.com, @outlook.com and @hotmail.com due to a problem at our mail provider. Emails that have already been sent are in a retry queue and will be delivered automatically once the issue has been resolved. Our mail provider is aware of the problem and is actively investigating it. We will provide an update as soon as more information becomes available.

2. 2026년 8월 6일 PM 2:18 UTCresolved

   The incident has been resolved, mails are being delivered again.

1. 2026년 7월 23일 PM 3:05 UTCinvestigating

   우리는 현재 HelloID WUS 로그인 포털에 영향을 미치는 정전을 경험하고 있습니다. 우리는 뿌리 원인을 조사하고 더 많은 정보가 가능한 한 빨리 업데이트를 제공 할 것입니다.

2. 2026년 7월 23일 PM 3:47 UTCinvestigating

   HelloID는 현재 웹 애플리케이션에 영향을 미치는 Azure West US 지역의 이슈에 영향을 미쳤습니다. Azure의 상태를 모니터링하고 새로운 정보를 사용할 때이 사건을 통해 업데이트를 제공합니다.

3. 2026년 7월 23일 PM 4:07 UTCinvestigating

   Microsoft Azure는 현재 진행중인 문제점에 대한 상태 페이지를 업데이트했습니다. 현재 상태에 액세스할 수 있습니다: https://azure.status.microsoft/en-gb/status 우리는 상황을 모니터링하고 더 많은 정보가 가능한 한 빨리 업데이트를 제공 할 것입니다.

4. 2026년 7월 23일 PM 7:17 UTCmonitoring

   HelloID 포털은 다시 사용할 수 있습니다. 우리는 안정성을 보장하기 위해 긴밀한 서비스를 모니터링하고 있습니다. Microsoft Azure는 최근 변경이 문제와 관련되었음을보고 롤백 작업은 현재 진행 중입니다. Azure telemetry는 복구의 초기 징후를 보여주고 Microsoft는 서비스 건강 및 트래픽 복구를 모니터링하고 있습니다.

5. 2026년 7월 24일 AM 6:19 UTCresolved

   HelloID 포털은 완전히 작동하고 몇 시간 동안 안정되었습니다. 더 이상 영향이 관찰되지 않았고,이 사건은 이제 해결되었습니다.

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

1. 2026년 7월 14일 PM 3:53 UTCinvestigating

   새로 생성 된 자동화 가변 및 기존 변수 값에 대한 최근 업데이트는 현재 반영되지 않습니다. Existing Automation Variables는 스크립트 실행 중에 사용할 수 있지만, 업데이트 된 것 대신 이전 값을 계속 사용합니다. 자동화 작업은 이 문제에 영향을 미치지 않습니다. 우리의 팀은 근본 원인을 조사하고 해결에 일하고 있습니다. 더 많은 정보가 가능한 한 빨리 업데이트됩니다.

2. 2026년 7월 14일 PM 6:34 UTCmonitoring

   우리는이 문제를 해결하는 수정을 구현했습니다. 새로 생성되거나 업데이트된 값을 반영하지 않는 자동화 변수와 문제가 계속되면, TOPdesk 셀프서비스 포털을 통해 티켓을 만들 수 있습니다. 우리의 지원 팀은 당신의 상황을 조사하고 가능한 빨리 원조할 것입니다.

3. 2026년 7월 15일 AM 10:20 UTCresolved

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

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

1. 2026년 6월 12일 AM 6:53 UTCinvestigating

   Some users have reported that they cannot access applications they should have access to. We are currently investigating the issue. We will share an update as soon as we have more information.

2. 2026년 6월 12일 AM 9:12 UTCinvestigating

   Our investigation has shown that these issues may also impact access to HelloID Service Automation products and delegated forms. Our teams are actively investigating the issue and working to resolve it as quickly as possible. We will continue to share updates through as new information becomes available.

3. 2026년 6월 12일 AM 10:21 UTCidentified

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

4. 2026년 6월 12일 PM 1:53 UTCmonitoring

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

5. 2026년 6월 15일 AM 7:18 UTCresolved

   The issue has been resolved. Please note that it may be necessary to reassign the affected groups to ensure the credential sets are added correctly. If you continue to experience issues after reassigning the groups, please contact our support team: https://tools4ever-support.topdesk.net/ We apologize for any inconvenience caused.

1. 2026년 6월 8일 PM 2:24 UTCinvestigating

   SSO applications based on OpenID Connect are currently not working. The JWKS document returns the following error: “Something went wrong.” We are investigating the issue and will provide an update as soon as more information is available.

2. 2026년 6월 10일 AM 7:14 UTCidentified

   The issue has been identified, and a fix is scheduled to be implemented. To apply this fix, downtime of the HelloID customer portal is required. During the implementation, HelloID will be temporarily unavailable. This downtime will not affect any scheduled processes or planned executions during this period. We will create a separate statuspage incident for this maintenance window, where all relevant updates and progress information will be communicated.

3. 2026년 6월 10일 AM 8:24 UTCmonitoring

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

4. 2026년 6월 11일 PM 1:28 UTCresolved

   This incident has been resolved.

1. 2026년 4월 14일 PM 1:51 UTCidentified

   At this moment, we're experiencing issues with AD login to HelloID. We're investigating the issue.

2. 2026년 4월 14일 PM 2:00 UTCmonitoring

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

3. 2026년 4월 15일 PM 1:57 UTCresolved

   This incident has been resolved.

1. 2026년 4월 14일 AM 11:22 UTCinvestigating

   At this moment, we're currently experiencing an issue with processing an evaluation and/or enforcement. We're investigating the issue.

2. 2026년 4월 14일 PM 12:55 UTCmonitoring

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

3. 2026년 4월 14일 PM 12:56 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2026년 4월 15일 PM 1:57 UTCresolved

   This incident has been resolved.

1. 2026년 4월 14일 AM 11:19 UTCidentified

   At this moment, we're experiencing an issue with HelloID where you can ancounter the errormessage "'Enable-RemoteMailbox' is not recognized". We're investigating the issue

2. 2026년 4월 14일 PM 12:55 UTCidentified

   We are continuing to work on a fix for this issue.

3. 2026년 4월 15일 PM 1:53 UTCmonitoring

   A fix has been implemented within the newest HelloID agent version. Please make sure your HelloID agent is updated to the most recent version to ensure the fix is applied. We will continue to monitor the results.

4. 2026년 4월 16일 PM 1:07 UTCresolved

   This incident has been resolved.

1. 2026년 4월 2일 AM 9:02 UTCinvestigating

   We are experiencing an issue where only a limited number of actions are started in HelloID through the on-premise agent, which may result in delays or timeouts. Our team is actively investigating the cause.

2. 2026년 4월 2일 AM 10:08 UTCresolved

   The issue has been resolved, we'll keep monitoring the situation.

1. 2026년 3월 19일 PM 1:16 UTCinvestigating

   We are experiencing an issue where only a limited number of actions are started in HelloID through the on-premise agent, which may result in delays or timeouts. Our team is actively investigating the cause.

2. 2026년 3월 20일 AM 11:01 UTCidentified

   We have rolled out a hotfix to mitigate the impact of these issues. We are closely monitoring the situation and will continue to actively monitor performance.

3. 2026년 3월 20일 PM 4:03 UTCmonitoring

   A new hotfix has been deployed. We expect this to improve the degraded performance, and under normal usage conditions, regular performance levels should be restored.

4. 2026년 3월 25일 AM 9:33 UTCresolved

   The issue has been resolved, we'll keep monitoring the situation.

1. 2026년 3월 2일 PM 12:55 UTCidentified

   At the moment, the Built-in Azure AD Actions cannot be executed. We are aware of the issue and are currently working on a hotfix to resolve it. We apologize for the inconvenience.

2. 2026년 3월 2일 PM 1:30 UTCresolved

   A hotfix has been implemented, and the actions should now be executed successfully again. We'll keep monitoring the situation.

1. 2026년 2월 25일 AM 11:05 UTCmonitoring

   We are currently experiencing issues with the delivery of emails to the domains @live.nl, @msn.com, @outlook.com, and @hotmail.com. To restore our email reputation, we have disabled email sending from training tenants. This is a preventive measure to ensure that emails to these domains can be delivered correctly again as soon as possible. For more information about the original incident, please refer to: https://helloid.statuspage.io/incidents/n6pl5ykzxv45 We will keep you informed of further developments via the status page.

2. 2026년 2월 26일 PM 2:14 UTCresolved

   After investigation, it has been determined that the issue is not related to HelloID, nor to the mail provider used by HelloID. As a result, the precautionary measure to disable the mail functionality in the training tenants is no longer necessary. The mail functionality has therefore been re-enabled in the training tenants.

1. 2026년 2월 24일 AM 9:06 UTCinvestigating

   We’re currently experiencing issues with email delivery to the domains @live.nl, @msn.com, @outlook.com and @hotmail.com due to a problem at our mail provider. Emails that have already been sent are in a retry queue and will be delivered automatically once the issue has been resolved. Our mail provider is aware of the problem and is actively investigating it. We will provide an update as soon as more information becomes available.

2. 2026년 2월 26일 AM 8:36 UTCmonitoring

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

3. 2026년 2월 26일 PM 1:32 UTCresolved

   After investigation, it has been determined that the issue is not related to HelloID, nor to the mail provider used by HelloID.

1. 2026년 2월 21일 AM 9:56 UTCidentified

   We are currently experiencing an issue where the HelloID on-premise agent may have lost its connection and did not automatically recover. You can resolve this by manually restarting the three HelloID services. For instructions, see: https://docs.helloid.com/en/agent/restart-an-agent.html We are actively working on a permanent solution for this connectivity issue. Our apologies for the inconvenience.

2. 2026년 2월 23일 AM 10:21 UTCmonitoring

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

3. 2026년 3월 25일 AM 9:33 UTCresolved

   The issue has been resolved, we'll keep monitoring the situation.

1. 2026년 2월 20일 AM 9:04 UTCinvestigating

   We are experiencing an issue where only a limited number of actions are started in HelloID through the on-premise agent, which may result in delays or timeouts. Our team is actively investigating the cause.

2. 2026년 2월 20일 AM 9:44 UTCmonitoring

   A fix has been implemented. In some cases, the connection to the HelloID on-premise agent may have been interrupted. The connection should restore automatically or can be re-established by restarting the HelloID services. We will continue to monitor the situation.

3. 2026년 2월 20일 PM 3:11 UTCresolved

   This incident has been resolved.

1. 2025년 12월 10일 PM 12:01 UTCidentified

   We have identified an issue may cause some HelloID evaluations or enforcements to fail. We are currently preparing a fix. In the meantime, if an evaluation or enforcement fails, please retry the action until it succeeds.

2. 2025년 12월 10일 PM 12:19 UTCidentified

   We are continuing to work on a fix for this issue.

3. 2025년 12월 11일 PM 2:22 UTCmonitoring

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

4. 2025년 12월 12일 AM 8:01 UTCresolved

   The issue has been resolved, we'll keep monitoring the situation.

1. 2025년 11월 18일 PM 12:03 UTCidentified

   We are experiencing network issues in HelloID due to Global Cloudflare network issues. More information can be found on this page - https://www.cloudflarestatus.com/

2. 2025년 11월 18일 PM 5:51 UTCresolved

   Cloudflare services are currently operating normally. We are no longer observing elevated errors or latency.

1. 2025년 11월 12일 PM 12:50 UTCinvestigating

   At this moment, we're experiencing slow responses within HelloID. We're investigating the issue.

2. 2025년 11월 12일 PM 1:03 UTCidentified

   The issue has been identified and a fix has been implemented

3. 2025년 11월 12일 PM 2:24 UTCresolved

   The issue has been resolved, we'll keep monitoring the situation.

1. 2025년 9월 9일 AM 8:33 UTCinvestigating

   We’re currently experiencing a visual bug in the field mapping interface, where all actions appear as configured. This display is incorrect and does not reflect the actual configuration. Please note: this is a visual issue only and does not impact any actions in the target system.

2. 2025년 9월 10일 AM 8:45 UTCidentified

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

3. 2025년 9월 10일 AM 8:52 UTCidentified

   We will start implementing the fix for the field mapping display issue at 11:00 CEST. No impact on system functionality is expected during this process. We’ll provide an update once the deployment is complete.

4. 2025년 9월 10일 AM 9:30 UTCmonitoring

   A fix has been deployed to resolve the display issue in field mapping. If you don’t see the changes right away, try clearing your browser cache. We will continue to monitor the results closely.

5. 2025년 9월 10일 AM 11:58 UTCresolved

   The visual bug in the field mapping display has been resolved. If the changes are not immediately visible, please refresh your browser cache. In case the issue persists, please contact Tools4ever support.