52 Helloid incidents · 2023年1月 — official updates, affected components, duration and resolution details.
現在、HelloIDで問題が発生しています。 基礎となるデータベースが到達できないため、テナントは利用できません。 原因はAzureと関連しているようですが、まだ調査中です。 皆様のお越しをお待ちしております。 詳しくは、サービスデスクにてチケットをお送りください.
当社の調査では、顧客データベースが影響を受けていないことを示しています。 すべての顧客のポータルは、この時間を通して正常に動作しています。 ありがとうございます。 ご不明な点がございましたら、サービスデスクにてチケットをお送りください.
公式のインシデント更新を自動翻訳しています。
現在、HelloIDポータルにアクセスし、ログインして問題が発生しています。 原因を調査しています。 詳しくは、こちらから更新をいたします。 アップデートを直接受け取りませんか? サポートポータルからチケットを作成してください.
Cloudflareは、ステータスページで更新を投稿しました。 問題はHelloIDではなく、最近ファームウェアのアップデートを受けたファイアウォールで示しています。 Cloudflareによると、この問題は、これらのファイアウォールのベンダーによって解決する必要があります。 https://www.cloudflarestatus.com/incidents/dk2obcyw2aew
公式のインシデント更新を自動翻訳しています。
現在、Elastic レポートの問題が発生しています。 Elastic にログオンすると期待どおりに動作しますが、レポートは表示できません。 現在、課題を調査中です。 API の使用は影響を受けるべきではありません.
問題は解決しました。 今後も状況を監視し、すべてが安定しているようにします.
公式のインシデント更新を自動翻訳しています。
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.
現在、HelloID WUS のログインポータルに影響する停電が発生しています。 根本的な原因を調べ、情報が増え次第に更新を行います.
HelloID は、Web アプリケーションに影響を及ぼす Azure West US 領域の問題の影響を受けています。 Azureのステータスを監視し、このインシデントを通じて新しい情報を公開する予定です.
Microsoft Azureは、現在進行中の問題に関するステータスページも更新しました。 ステータスページはこちら: https://azure.status.microsoft/en-gb/status 今後も状況を監視し、情報が増え次第に更新をしていきます.
HelloID ポータルは、再び利用できます。 安定を確保するために、サービスを密接に監視し続けています。 Microsoft Azure は、最近の変更が問題に強く関連し、現在進行中です。 Azureのテレメトリーは回復の初期の徴候を示し、マイクロソフトはサービスの健康および交通回復を監視しています.
HelloID ポータルは、いくつかの時間のために完全に運用および安定しています。 さらなる影響が認められず、この事件が解決しました.
公式のインシデント更新を自動翻訳しています。
既存の変数値に対するオートメーション変数と最近の更新は、現在反映されていない。 既存の Automation 変数はスクリプトの実行中に利用できませんが、更新されたものの代わりに、以前の値を使用します。 自動化タスクのスケジュールは、この問題の影響を受けません。 私たちのチームは、根本原因を積極的に調査し、解決に取り組んでいます。 情報が増え次第、順次更新をいたします.
この問題を解決する修正を行いました。 新しく作成した値や更新された値を反映していない自動化変数で問題が発生した場合は、TOPdeskセルフサービスポータルを通じてチケットを作成してください。 当社のサポートチームは、お客様の状況を調査し、可能な限り迅速に対応いたします.
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
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.
