Störungsverlauf von Helloid

1. 28. August 2026 um 12:27 UTCinvestigating

   Wir haben derzeit Probleme mit Elastic-Berichten. Die Anmeldung bei Elastic funktioniert wie erwartet, aber die Berichte können nicht angezeigt werden. Wir untersuchen derzeit das Problem. Die Verwendung der API sollte nicht beeinträchtigt werden.

2. 28. August 2026 um 18:13 UTCresolved

   Das Problem ist gelöst. Wir werden die Situation weiter beobachten, um sicherzustellen, dass alles stabil bleibt.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 5. August 2026 um 14:29 UTCinvestigating

   Wir haben derzeit Probleme mit der E-Mail-Zustellung an die Domains @live.nl, @msn.com, @outlook.com und @hotmail.com aufgrund eines Problems bei unserem Mail-Provider. E-Mails, die bereits gesendet wurden, befinden sich in einer Warteschlange und werden automatisch zugestellt, sobald das Problem behoben wurde. Unser Mailanbieter ist sich des Problems bewusst und untersucht es aktiv. Wir werden ein Update bereitstellen, sobald weitere Informationen verfügbar sind.

2. 6. August 2026 um 14:18 UTCresolved

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

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 23. Juli 2026 um 15:05 UTCinvestigating

   Wir erleben derzeit einen Ausfall der HelloID WUS-Login-Portale. Wir untersuchen die Ursache und werden ein Update bereitstellen, sobald weitere Informationen verfügbar sind.

2. 23. Juli 2026 um 15:47 UTCinvestigating

   HelloID ist derzeit von einem Problem in der Region Azure West US betroffen, das sich auf Webanwendungen auswirkt. Wir überwachen den Status von Azure und werden durch diesen Vorfall ein Update bereitstellen, wenn neue Informationen verfügbar sind.

3. 23. Juli 2026 um 16:07 UTCinvestigating

   Microsoft Azure hat nun auch seine Statusseite bezüglich des laufenden Problems aktualisiert. Die Statusseite finden Sie hier: https://azure.status.microsoft/en-gb/status Wir beobachten die Situation weiterhin und werden weitere Updates bereitstellen, sobald weitere Informationen verfügbar sind.

4. 23. Juli 2026 um 19:17 UTCmonitoring

   Die HelloID-Portale sind wieder verfügbar. Wir überwachen den Dienst weiterhin genau, um Stabilität zu gewährleisten. Microsoft Azure hat berichtet, dass eine kürzliche Änderung stark mit dem Problem korreliert war und dass derzeit Rollback-Aktionen durchgeführt werden. Azure Telemetrie zeigt erste Anzeichen einer Wiederherstellung, und Microsoft überwacht den Zustand des Dienstes und die Wiederherstellung des Datenverkehrs.

5. 24. Juli 2026 um 06:19 UTCresolved

   Die HelloID-Portale sind seit einiger Zeit voll funktionsfähig und stabil. Es wurden keine weiteren Auswirkungen beobachtet, und dieser Vorfall ist nun behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 14. Juli 2026 um 15:53 UTCinvestigating

   Neu erstellte Automatisierungsvariablen und aktuelle Aktualisierungen bestehender Variablenwerte werden derzeit nicht berücksichtigt. Bestehende Automatisierungsvariablen bleiben während der Skriptausführung verfügbar, verwenden jedoch weiterhin ihre vorherigen Werte anstelle der aktualisierten. Geplante Automatisierungsaufgaben sind von diesem Problem nicht betroffen. Unser Team untersucht aktiv die Ursache und arbeitet an einer Lösung. Wir werden weitere Updates bereitstellen, sobald weitere Informationen verfügbar sind.

2. 14. Juli 2026 um 18:34 UTCmonitoring

   Wir haben einen Fix implementiert, der dieses Problem löst. Wenn Sie weiterhin Probleme mit Automatisierungsvariablen haben, die keine neu erstellten oder aktualisierten Werte widerspiegeln, erstellen Sie bitte ein Ticket über das TOPdesk-Selfservice-Portal. Unser Support-Team wird Ihre Situation untersuchen und Sie so schnell wie möglich unterstützen.

3. 15. Juli 2026 um 10:20 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 12. Juni 2026 um 06: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. 12. Juni 2026 um 09: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. 12. Juni 2026 um 10:21 UTCidentified

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

4. 12. Juni 2026 um 13:53 UTCmonitoring

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

5. 15. Juni 2026 um 07: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. 8. Juni 2026 um 14: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. 10. Juni 2026 um 07: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. 10. Juni 2026 um 08:24 UTCmonitoring

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

4. 11. Juni 2026 um 13:28 UTCresolved

   This incident has been resolved.

1. 14. April 2026 um 13:51 UTCidentified

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

2. 14. April 2026 um 14:00 UTCmonitoring

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

3. 15. April 2026 um 13:57 UTCresolved

   This incident has been resolved.

1. 14. April 2026 um 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. 14. April 2026 um 12:55 UTCmonitoring

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

3. 14. April 2026 um 12:56 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 15. April 2026 um 13:57 UTCresolved

   This incident has been resolved.

1. 14. April 2026 um 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. 14. April 2026 um 12:55 UTCidentified

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

3. 15. April 2026 um 13: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. 16. April 2026 um 13:07 UTCresolved

   This incident has been resolved.

1. 2. April 2026 um 09: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. 2. April 2026 um 10:08 UTCresolved

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

1. 19. März 2026 um 13: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. 20. März 2026 um 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. 20. März 2026 um 16: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. 25. März 2026 um 09:33 UTCresolved

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

1. 2. März 2026 um 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. 2. März 2026 um 13:30 UTCresolved

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

1. 25. Februar 2026 um 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. 26. Februar 2026 um 14: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. 24. Februar 2026 um 09: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. 26. Februar 2026 um 08:36 UTCmonitoring

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

3. 26. Februar 2026 um 13: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. 21. Februar 2026 um 09: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. 23. Februar 2026 um 10:21 UTCmonitoring

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

3. 25. März 2026 um 09:33 UTCresolved

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

1. 20. Februar 2026 um 09: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. 20. Februar 2026 um 09: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. 20. Februar 2026 um 15:11 UTCresolved

   This incident has been resolved.

1. 10. Dezember 2025 um 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. 10. Dezember 2025 um 12:19 UTCidentified

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

3. 11. Dezember 2025 um 14:22 UTCmonitoring

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

4. 12. Dezember 2025 um 08:01 UTCresolved

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

1. 18. November 2025 um 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. 18. November 2025 um 17:51 UTCresolved

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

1. 12. November 2025 um 12:50 UTCinvestigating

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

2. 12. November 2025 um 13:03 UTCidentified

   The issue has been identified and a fix has been implemented

3. 12. November 2025 um 14:24 UTCresolved

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

1. 9. September 2025 um 08: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. 10. September 2025 um 08:45 UTCidentified

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

3. 10. September 2025 um 08: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. 10. September 2025 um 09: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. 10. September 2025 um 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.