Helloid driftsforstyrrelser

1. 28. august 2026 kl. 12.27 UTCinvestigating

   Vi oplever i øjeblikket problemer med Elastiske rapporter. Logning på Elastic virker som forventet, men rapporterne kan ikke vises. Vi undersøger i øjeblikket spørgsmålet. Brug af API bør ikke påvirkes.

2. 28. august 2026 kl. 18.13 UTCresolved

   Spørgsmålet er løst. Vi vil fortsat overvåge situationen for at sikre, at alt forbliver stabilt.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 5. august 2026 kl. 14.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. 6. august 2026 kl. 14.18 UTCresolved

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

1. 23. juli 2026 kl. 15.05 UTCinvestigating

   Vi oplever i øjeblikket en afbrydelse, der påvirker HelloID WUS login portaler. Vi undersøger den grundlæggende årsag og vil give en opdatering, så snart mere information er tilgængelig.

2. 23. juli 2026 kl. 15.47 UTCinvestigating

   HelloID er i øjeblikket påvirket af et problem i Azure West US-regionen, der påvirker web-applikationer. Vi overvåger Azure status og vil give en opdatering gennem denne hændelse, når nye oplysninger er tilgængelige.

3. 23. juli 2026 kl. 16.07 UTCinvestigating

   Microsoft Azure har nu også opdateret sin status side om det igangværende problem. Du kan få adgang til statusside her: https: / / azure.status.microsoft / en- gb / status Vi fortsætter med at overvåge situationen og vil give yderligere opdateringer, så snart mere information bliver tilgængelig.

4. 23. juli 2026 kl. 19.17 UTCmonitoring

   HelloID portaler er tilgængelige igen. Vi fortsætter med at overvåge tjenesten nøje for at sikre stabilitet. Microsoft Azure har rapporteret, at en nylig ændring var stærkt forbundet med problemet, og at rollback handlinger er i gang i øjeblikket. Azure telemetri viser indledende tegn på inddrivelse, og Microsoft overvåger service sundhed og trafik opsving.

5. 24. juli 2026 kl. 06.19 UTCresolved

   HelloID portalerne har været fuldt operationelle og stabile i nogen tid. Der er ikke konstateret yderligere virkninger, og denne hændelse er nu løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 14. juli 2026 kl. 15.53 UTCinvestigating

   Nyskabte Automation Variabler og nylige opdateringer til eksisterende variable værdier er i øjeblikket ikke afspejles. Eksisterende Automation Variabler forbliver tilgængelige under script udførelse, men de fortsætter med at bruge deres tidligere værdier i stedet for de opdaterede. Planlagte Automation Opgaver er ikke påvirket af dette spørgsmål. Vores team undersøger sagen og arbejder på en beslutning. Vi vil give yderligere opdateringer, så snart mere information bliver tilgængelig.

2. 14. juli 2026 kl. 18.34 UTCmonitoring

   Vi har gennemført en løsning på dette problem. Hvis du fortsætter med at opleve problemer med automatiseringsvariabler, der ikke afspejler nyoprettede eller opdaterede værdier, skal du oprette en billet gennem TOPdesk selvbetjeningsportal. Vores support team vil undersøge din situation og hjælpe dig så hurtigt som muligt.

3. 15. juli 2026 kl. 10.20 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 12. juni 2026 kl. 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 kl. 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 kl. 10.21 UTCidentified

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

4. 12. juni 2026 kl. 13.53 UTCmonitoring

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

5. 15. juni 2026 kl. 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 kl. 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 kl. 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 kl. 08.24 UTCmonitoring

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

4. 11. juni 2026 kl. 13.28 UTCresolved

   This incident has been resolved.

1. 14. april 2026 kl. 13.51 UTCidentified

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

2. 14. april 2026 kl. 14.00 UTCmonitoring

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

3. 15. april 2026 kl. 13.57 UTCresolved

   This incident has been resolved.

1. 14. april 2026 kl. 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 kl. 12.55 UTCmonitoring

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

3. 14. april 2026 kl. 12.56 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 15. april 2026 kl. 13.57 UTCresolved

   This incident has been resolved.

1. 14. april 2026 kl. 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 kl. 12.55 UTCidentified

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

3. 15. april 2026 kl. 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 kl. 13.07 UTCresolved

   This incident has been resolved.

1. 2. april 2026 kl. 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 kl. 10.08 UTCresolved

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

1. 19. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 09.33 UTCresolved

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

1. 2. marts 2026 kl. 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. marts 2026 kl. 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 kl. 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 kl. 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 kl. 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 kl. 08.36 UTCmonitoring

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

3. 26. februar 2026 kl. 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 kl. 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 kl. 10.21 UTCmonitoring

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

3. 25. marts 2026 kl. 09.33 UTCresolved

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

1. 20. februar 2026 kl. 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 kl. 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 kl. 15.11 UTCresolved

   This incident has been resolved.

1. 10. december 2025 kl. 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. december 2025 kl. 12.19 UTCidentified

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

3. 11. december 2025 kl. 14.22 UTCmonitoring

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

4. 12. december 2025 kl. 08.01 UTCresolved

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

1. 18. november 2025 kl. 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 kl. 17.51 UTCresolved

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

1. 12. november 2025 kl. 12.50 UTCinvestigating

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

2. 12. november 2025 kl. 13.03 UTCidentified

   The issue has been identified and a fix has been implemented

3. 12. november 2025 kl. 14.24 UTCresolved

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

1. 9. september 2025 kl. 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 kl. 08.45 UTCidentified

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

3. 10. september 2025 kl. 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 kl. 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 kl. 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.