Helloid outage history

We are currently experiencing issues with Elastic reports. Logging in to Elastic works as expected, but the reports cannot be displayed. We are currently investigating the issue. Using the API should not be affected.

The issue has been resolved. We’ll continue to monitor the situation to ensure everything remains stable.

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.

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

We are currently experiencing an outage affecting the HelloID WUS login portals. We are investigating the root cause and will provide an update as soon as more information is available.

HelloID is currently affected by an issue in the Azure West US region that is impacting web applications. We are monitoring Azure’s status and will provide an update through this incident when new information is available.

Microsoft Azure has now also updated its status page regarding the ongoing issue. You can access the statuspage here: https://azure.status.microsoft/en-gb/status We are continuing to monitor the situation and will provide further updates as soon as more information becomes available.

The HelloID portals are available again. We are continuing to monitor the service closely to ensure stability. Microsoft Azure has reported that a recent change was strongly correlated with the issue and that rollback actions are currently in progress. Azure telemetry is showing initial signs of recovery, and Microsoft is monitoring service health and traffic recovery.

The HelloID portals have been fully operational and stable for some time. No further impact has been observed, and this incident is now resolved.

Newly created Automation Variables and recent updates to existing variable values are currently not being reflected. Existing Automation Variables remain available during script execution, but they continue to use their previous values instead of the updated ones. Scheduled Automation Tasks are not affected by this issue. Our team is actively investigating the root cause and working on a resolution. We will provide further updates as soon as more information becomes available.

We have implemented a fix that resolves this issue. If you continue to experience problems with automation variables not reflecting newly created or updated values, please create a ticket through the TOPdesk selfservice portal. Our support team will investigate your situation and assist you as quickly as possible.

This incident has been resolved.

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.

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.

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

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

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.

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.

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.

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

This incident has been resolved.

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

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

This incident has been resolved.

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

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

We are continuing to monitor for any further issues.

This incident has been resolved.

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

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

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.

This incident has been resolved.

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.

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

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.

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.

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.

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

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.

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

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.

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.

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.

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

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

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.

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

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

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.

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.

This incident has been resolved.

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.

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

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

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

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/

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

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

The issue has been identified and a fix has been implemented

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

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.

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

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.

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.

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.