Historial de interrupciones de Helloid

1. 28 de agosto de 2026 a las 12:27 UTCinvestigating

   Actualmente estamos experimentando problemas con informes elásticos. Inicie sesión en obras elásticas como se esperaba, pero los informes no se pueden mostrar. Actualmente estamos investigando la cuestión. Utilizar la API no debe ser afectada.

2. 28 de agosto de 2026 a las 18:13 UTCresolved

   La cuestión se ha resuelto. Seguiremos monitoreando la situación para asegurar que todo permanezca estable.

Traducido automáticamente desde la actualización oficial del incidente.

1. 5 de agosto de 2026 a las 14:29 UTCinvestigating

   Actualmente estamos experimentando problemas con la entrega de correo electrónico a los dominios @live.nl, @msn.com, @outlook.com y @hotmail.com debido a un problema en nuestro proveedor de correo. Los correos electrónicos que ya se han enviado están en una cola de reingreso y se entregarán automáticamente una vez resuelto el problema. Nuestro proveedor de correos es consciente del problema y está investigando activamente. Proporcionaremos una actualización tan pronto como se disponga de más información.

2. 6 de agosto de 2026 a las 14:18 UTCresolved

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

Traducido automáticamente desde la actualización oficial del incidente.

1. 23 de julio de 2026 a las 15:05 UTCinvestigating

   Actualmente estamos experimentando un outage que afecta a los portales de inicio de sesión de HelloID WUS. Estamos investigando la causa raíz y proporcionaremos una actualización tan pronto como esté disponible más información.

2. 23 de julio de 2026 a las 15:47 UTCinvestigating

   Actualmente, HelloID se ve afectada por un problema en la región de Azure West US que está afectando aplicaciones web. Estamos monitoreando el estado de Azure y proporcionaremos una actualización a través de este incidente cuando haya nueva información disponible.

3. 23 de julio de 2026 a las 16:07 UTCinvestigating

   Microsoft Azure también ha actualizado su página de estado sobre el tema en curso. Puede acceder a la página de estado aquí: https://azure.status.microsoft/en-gb/status Seguimos vigilando la situación y proporcionaremos más actualizaciones tan pronto como se disponga de más información.

4. 23 de julio de 2026 a las 19:17 UTCmonitoring

   Los portales de HelloID están disponibles de nuevo. Seguimos vigilando de cerca el servicio para garantizar la estabilidad. Microsoft Azure ha informado de que un cambio reciente estaba fuertemente correlacionado con la cuestión y que actualmente se están llevando a cabo acciones de retroceso. La telemetría Azure muestra signos iniciales de recuperación, y Microsoft está monitoreando la salud del servicio y la recuperación de tráfico.

5. 24 de julio de 2026 a las 6:19 UTCresolved

   Los portales de HelloID han estado completamente operativos y estables durante algún tiempo. No se ha observado ningún nuevo impacto, y este incidente se resuelve ahora.

Traducido automáticamente desde la actualización oficial del incidente.

1. 14 de julio de 2026 a las 15:53 UTCinvestigating

   Actualmente no se están reflejando las variables de automatización creadas recientemente y las actualizaciones recientes de los valores variables existentes. Las variables existentes de automatización permanecen disponibles durante la ejecución del script, pero siguen utilizando sus valores anteriores en lugar de los actualizados. Las tareas de automatización programadas no se ven afectadas por este problema. Nuestro equipo está investigando activamente la causa raíz y trabajando en una resolución. Proporcionaremos más actualizaciones tan pronto como se disponga de más información.

2. 14 de julio de 2026 a las 18:34 UTCmonitoring

   Hemos implementado una solución que resuelve esta cuestión. Si sigues experimentando problemas con variables de automatización que no reflejan valores recién creados o actualizados, por favor cree un ticket a través del portal de autoservicio TOPdesk. Nuestro equipo de apoyo investigará su situación y le ayudará lo antes posible.

3. 15 de julio de 2026 a las 10:20 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 12 de junio de 2026 a las 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. 12 de junio de 2026 a las 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. 12 de junio de 2026 a las 10:21 UTCidentified

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

4. 12 de junio de 2026 a las 13:53 UTCmonitoring

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

5. 15 de junio de 2026 a las 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. 8 de junio de 2026 a las 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 de junio de 2026 a las 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. 10 de junio de 2026 a las 8:24 UTCmonitoring

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

4. 11 de junio de 2026 a las 13:28 UTCresolved

   This incident has been resolved.

1. 14 de abril de 2026 a las 13:51 UTCidentified

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

2. 14 de abril de 2026 a las 14:00 UTCmonitoring

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

3. 15 de abril de 2026 a las 13:57 UTCresolved

   This incident has been resolved.

1. 14 de abril de 2026 a las 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 de abril de 2026 a las 12:55 UTCmonitoring

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

3. 14 de abril de 2026 a las 12:56 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 15 de abril de 2026 a las 13:57 UTCresolved

   This incident has been resolved.

1. 14 de abril de 2026 a las 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 de abril de 2026 a las 12:55 UTCidentified

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

3. 15 de abril de 2026 a las 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 de abril de 2026 a las 13:07 UTCresolved

   This incident has been resolved.

1. 2 de abril de 2026 a las 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. 2 de abril de 2026 a las 10:08 UTCresolved

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

1. 19 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de marzo de 2026 a las 9:33 UTCresolved

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

1. 2 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de febrero de 2026 a las 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 de febrero de 2026 a las 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 de febrero de 2026 a las 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. 26 de febrero de 2026 a las 8:36 UTCmonitoring

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

3. 26 de febrero de 2026 a las 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 de febrero de 2026 a las 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. 23 de febrero de 2026 a las 10:21 UTCmonitoring

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

3. 25 de marzo de 2026 a las 9:33 UTCresolved

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

1. 20 de febrero de 2026 a las 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. 20 de febrero de 2026 a las 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. 20 de febrero de 2026 a las 15:11 UTCresolved

   This incident has been resolved.

1. 10 de diciembre de 2025 a las 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 de diciembre de 2025 a las 12:19 UTCidentified

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

3. 11 de diciembre de 2025 a las 14:22 UTCmonitoring

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

4. 12 de diciembre de 2025 a las 8:01 UTCresolved

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

1. 18 de noviembre de 2025 a las 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 de noviembre de 2025 a las 17:51 UTCresolved

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

1. 12 de noviembre de 2025 a las 12:50 UTCinvestigating

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

2. 12 de noviembre de 2025 a las 13:03 UTCidentified

   The issue has been identified and a fix has been implemented

3. 12 de noviembre de 2025 a las 14:24 UTCresolved

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

1. 9 de septiembre de 2025 a las 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. 10 de septiembre de 2025 a las 8:45 UTCidentified

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

3. 10 de septiembre de 2025 a las 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. 10 de septiembre de 2025 a las 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. 10 de septiembre de 2025 a las 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.