57 Samanage incidents · 2024年4月 — official updates, affected components, duration and resolution details.
我们目前正在调查一个影响太阳视窗服务台的问题。 一些用户此时可能无法访问该应用程序. 我们的团队正在积极工作,以查明原因,尽快恢复服务。 一旦获得更多信息,我们将分享另一个最新情况.
我们的调查发现了根本问题。 已部署纠正措施,该处仍在积极监测,以核查稳定情况并证实完全解决.
该系统已经恢复并正常运行。 我们正在继续监测服务业绩和稳定性,以确保纠正措施依然有效.
系统在修复后继续正常运行. 监测工作仍在进行,目前没有观察到其他问题.
经过几分钟的监测,该系统继续正常运行. 我们正在指出这一问题已得到解决。 如需进一步协助,请与技术支持中心联系:technological [email protected].
自动翻译自官方事件更新。
目前,我们在整个平台显示最新信息的工作出现延误。 新的和更新的门票、评论、事件变化和实地更新——如状态和标题变化——可能比预期的出现时间长,或可能暂时显示过时的信息。 页面负荷时间也可能受到影响. 我们的团队已经确定了这一问题,并正在努力解决这一问题。 随着我们跨平台推出固定装置,一些延误可能会继续.
修复工作已经部署,我们正在积极处理其余积压的更新票。 在进行处理期间,一些更新工作可能继续被拖延,但我们预计,随着积压工作得到清理,延迟工作将会减少。 我们将继续对该系统进行监测,并随着处理的进展提供更多的更新.
这一事件已经得到解决.
自动翻译自官方事件更新。
目前,在平台上显示的最新资料出现延误。 新的并更新的入场券,评论,事件更改,以及状态和标题等外地更新,以及其他功能,有时更新和或显示过时信息的速度会很慢. 我们还看到页面负荷时间受到影响。 该小组已查明了这一问题并正在拟订一项决议。 当我们在月台上铺平时 你可能会遇到一些延误.
修复工作已经部署,我们正在积极处理剩余积压的更新票。 在处理过程中,一些更新的车票可能会继续被拖延。 我们期望这些拖延随着积压工作得到清理而得到解决。 我们将继续监测该系统,并随着处理进展提供进一步的最新资料.
我们正在部署固定装置后看到改进;我们正积极监测该系统,以确保业绩保持稳定,并确保所有被拖延的更新都得到充分处理.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们目前正在调查一个影响太阳视窗服务台的问题。 一些用户此时可能无法访问该应用程序. 我们的团队正在积极工作,以查明原因,尽快恢复服务。 一旦获得更多信息,我们将分享另一个最新情况.
我们正在继续调查这一问题.
应用程序再次开放,服务已经恢复。 我们的小组继续密切监测申请情况,以确保稳定。 如果发现任何其他问题,我们将提供另一个最新情况.
我们的小组继续密切监测申请情况,以确保稳定。 进一步更新一经提供,即予分享.
在经过长时间的监测之后,SolarWinds服务台现在正常运转。 此时,我们认为事件已经解决. 一旦调查完成,今后几天将分享根源分析。 如需额外援助或任何进一步问题,请与我们联系,地址是:technological [email protected].
自动翻译自官方事件更新。
我们目前正在调查一个影响SolarWinds服务服务台的问题,通过电子邮件创建的事件正在成功提交,确认信息正在发送,但新创建的事件可能没有出现在事件索引页面上。 我们的团队正在积极努力,找出根源,并尽快恢复正常的能见度. 一旦获得更多信息,我们将提供另一个最新情况.
我们正在继续调查SolarWinds服务台的一个问题,即尽管成功提交并发出确认信息,但事件索引页可能没有出现新的事件。 我们的团队正在努力查明原因并恢复正常的能见度。 一旦获得更多信息,我们将分享另一个最新情况.
我们查明了影响SolarWinds服务服务台的问题的根源,尽管成功提交,但事件索引页可能没有出现新的事件。 一旦获得更多信息,我们将分享另一个最新情况.
为纠正影响SolarWinds服务服务台的问题,已安装了一个固定装置,尽管已成功创建,但事件索引页上可能没有出现新的事件。 我们正在继续密切监测这项服务,以确保完全恢复正常的能见度.
在经过长时间的监测之后,SolarWinds服务台现在正常运转。 此时,我们认为事件已经解决. 如需额外援助或任何进一步问题,请与我们联系,地址是:technological [email protected].
自动翻译自官方事件更新。
我们目前正在调查一个影响SolarWinds服务服务台的问题,通过电子邮件创建的事件被成功提交并发送确认信息,但新创建的事件可能没有出现在事件索引页面上. 我们的团队正积极努力,找出原因,并尽快恢复正常的能见度. 一旦获得更多信息,我们将分享另一个最新情况.
我们已查明了报告问题的起因,并正在尽快解决。 谢谢你的耐心.
我们已完成了解决这个问题的工作,服务正在恢复正常。 通过电子邮件提交的事件现在应该如预期的那样适当出现在事件索引的网页上。 我们的小组将继续密切监测环境,以确保稳定,并证实这一问题已经得到全面解决。 我们赞赏你在努力解决这一问题时的耐心.
我们正在继续密切监测这种行为,而我们的小组则努力确认事件清单中一贯的能见度。 一旦获得更多信息,我们将分享另一个最新情况.
应用程序的总体性能正在改善。 我们的小组继续密切监测环境,以确保稳定,并证实不再出现问题。 我们将视需要分享其他最新情况.
经过长时间的监测之后,这个问题没有再出现,我们没有收到任何关于影响的其他报告。 服务正常运行,我们正在考虑解决这一事件。 如果你继续经历任何问题或需要进一步援助,请通过电子邮件联系我们,地址是:technological [email protected]。 我们的团队将很乐意提供帮助.
自动翻译自官方事件更新。
我们目前正在调查一个问题,即通过电子邮件制造的事件可能不会立即出现在SolarWinds服务服务台的事件清单中。 在我们的审查期间,我们确认正在成功地发出事件制造通知,通过直接链接可以查阅受影响的事件。 然而,这些事件可能迟迟没有出现在伊斯兰法院联盟内部的事件清单中。 我们的团队正在积极调查这种行为,努力确定原因. 一旦获得更多信息,我们将分享另一个最新情况.
我们目前正在监测这一问题。 我们的调查证实,事件正在成功发生,正在按预期发送通知电子邮件。 然而,通过电子邮件造成的一些事件可能并不立即出现在UI内的事件清单中,尽管它们仍然可以通过通知电子邮件中的直接联系进入。 我们正在继续密切监测这种行为,而我们的小组则努力确认事件清单中一贯的能见度。 一旦获得更多信息,我们将分享另一个最新情况.
我们的监测表明,影响事件能见度的问题已经得到解决。 我们继续密切监测这项服务,并没有发现任何进一步的问题。 此时,我们认为事件已经解决. 如需额外援助或任何进一步问题,请与我们联系,地址是:technological [email protected].
自动翻译自官方事件更新。
We are currently investigating reports of slow performance issues in SolarWinds Service Desk. Our team is working to resolve this as quickly as possible.
We have identified the cause of the reported issue and are actively working to implement a fix as quickly as possible. Thank you for your patience and understanding while we work toward a resolution.
We are seeing improved performance on our end and are continuing to monitor the situation closely. We are also working to confirm whether customers are experiencing similar improvements as we continue our efforts to ensure full service stability. We appreciate your patience and understanding during this time. We will provide another update as soon as additional information becomes available.
We have continued to monitor the service and have not observed any further issues. In addition, we have not received any new reports of slow performance. Based on our monitoring and the current system status, this incident is considered resolved. Should you require any further assistance or experience any additional issues, please do not hesitate to contact us at [email protected]. Thank you for your patience and cooperation throughout this process.
We are aware of an issue that caused the application to be unavailable for a few minutes. Our team is currently investigating the cause and monitoring the service to ensure it remains stable. Further updates will be posted here as more information becomes available.
The services are currently operating normally, and our engineering team is closely monitoring system performance to ensure continued stability. We will provide additional updates here if we observe any further impact or if additional action is required.
Following an extended monitoring period, the issue has not reappeared, and no further impact has been reported. Services are operating normally, and we consider this incident resolved. If you experience any additional issues or need assistance, please contact us at [email protected], and our team will be glad to help.
We are aware of an issue that caused the application to be unavailable for approximately two minutes. Our team is currently investigating the cause and monitoring the service to ensure it remains stable. Further updates will be posted here as more information becomes available.
We are continuing to investigate this issue.
The services are currently operating normally, and our engineering team is closely monitoring system performance to ensure continued stability. We will provide additional updates here if we observe any further impact or if additional action is required.
After an extended period of monitoring, the issue has not resurfaced and we have not received any additional reports of impact. Service is operating normally and we are considering this incident resolved. If you continue to experience any issues or need further assistance, please contact us via email at [email protected], and our team will be happy to help.
We are currently investigating reports of slow performance and intermittent Error 500 issues in SolarWinds Service Desk. Our team is working to resolve this as quickly as possible.
We've identified the cause of the reported issue and are working on a fix as quickly as possible. Thank you for your patience.
We have completed the fix for this issue and will continue to monitor the situation to ensure stability.
We have observed unexpected behavior following the recent fix and are currently reviewing the issue. Our team is continuing to investigate while working to ensure full stability. We appreciate your patience and will provide further updates as soon as more information becomes available.
We are actively investigating continued unexpected behavior following a recent fix. Our team is working to ensure full stability. We appreciate your patience and will share another update as soon as more information is available.
We are seeing improved results on our end and are continuing to monitor performance closely. We are also working to confirm whether customers are seeing similar improvement while we continue to ensure full stability. We appreciate your patience and will provide another update as soon as more information becomes available.
We have continued to monitor the service and have not observed any further issues. Additionally, we have not received any new reports of slow performance or Error 500 errors. At this time, the incident is considered resolved. If further assistance is needed, please contact [email protected]. Thank you for your patience throughout this process.
We have received reports of overlapping text fields in Incident/Service Request tickets and are currently investigating the issue.
We have identified the cause of the overlapping text fields and are currently working on a fix. We will provide updates as soon as progress is made. Thank you for your patience and understanding.
We are still working on fixing the issue. We will continue to monitor the situation and provide updates as they become available.
We will deploy a fix shortly. We will provide an update once it has been deployed.
We are in the process of deploying the fix. We will keep you updated as progress continues.
We have completed the deployment of the fix for this issue and will continue to monitor the situation to ensure stability.
This issue has been resolved.
We are currently experiencing performance issues in the Service Desk Application, and our team is investigating. This impacts actions such as navigating through the Incidents page and other areas of the app.
We have identified elevated load on the database layer in our US Service Desk environment. This is leading to slow page loads, delayed data population, and intermittent 504 Gateway Timeout errors for some customers. Our team is actively working on remediation to reduce database load and restore normal performance. During this time, the application may run more slowly than normal. We will provide the next update within 30 minutes or sooner as we make progress.
We are still actively working on reducing the elevated database load in our US Service Desk environment. The underlying issue has been identified, and our team is continuing remediation efforts to stabilize performance.
We are continuing to work on a fix for this issue and further reducing the elevated database load in our US Service Desk environment. Some users may still experience intermittent slowness or timeouts while we complete these changes. We will provide another update within 30 minutes or as soon as we have more information.
We have implemented a fix for the database load issue affecting our US Service Desk environment; we are restarting a set of frontend services to complete remediation. Users should now begin to see improved performance and fewer timeouts as these changes take effect. Our team will continue to closely monitor the environment and will provide another update once performance is fully stabilized.
We have resolved the database load issue affecting our US Service Desk environment and restarted the impacted frontend services. Since then, performance has remained stable under monitoring, and we are no longer observing elevated errors or timeouts. This incident is now closed. If you continue to experience slowness or errors, please contact SolarWinds Support or open a ticket so we can investigate further.
We are investigating an issue where some users are unable to fully load service (catalog) requests. Affected pages may briefly appear and then show blank or incomplete content. Our engineering team is actively investigating the cause and working to restore full functionality. We will provide updates on this page as more information becomes available. If you are impacted and need assistance, please contact SolarWinds Support through your usual channels.
We are continuing to investigate this issue.
Our investigation has determined that this issue is limited to a subset of Service Desk service requests and service catalog items and does not affect all users or all catalogs. We are continuing to investigate the underlying cause and will provide additional updates on this page as our work progresses.
We have identified the root cause of the issue. It occurs when a process workflow includes a Send Notification action that sends an email to a user or email address that does not have a valid user account within the affected Service Desk instance. Our engineering team is actively working on a fix. Additional updates will be provided on this page as progress continues.
We are actively working on a fix for this issue. As a reminder, the cause occurs when a process workflow includes a Send Notification action that sends an email to a user or email address that does not have a valid user account in the affected Service Desk instance. As a temporary workaround, service desk administrators can update the affected workflows so that Send Notification actions are configured to send emails to a named user with a valid Service Desk account instead of an email address that is not associated with a user. We will provide further updates on this page as our work progresses.
Our engineering team has prepared a fix for this issue, and the deployment process has started. During the deployment window, some users may experience brief slowdowns or intermittent delays; we expect any impact to be minimal and temporary. We will provide a further update on this page once the deployment has finished.
Our Engineering team has successfully applied a fix and is applying it retroactively to resolve the issue for all affected users. Any interruptions during this process should be minimal. We will provide another update in the next hour.
Our Engineering team is continuously working on applying a fix to the data for all affected users. Further updates will be provided in the next hour.
Our Engineering team is actively deploying a remediation to address issues resulting in page load failures, blank pages, or incomplete content. Further updates will be provided as progress continues.
Our team is in the final stages of deploying the fix. We expect completion shortly and will share an update immediately.
The fix deployment is now complete, and our team is closely monitoring the results to ensure stability.
We are marking this issue as resolved, as we have confirmed that all new service requests work correctly and previously submitted requests work as intended. If the issue resurfaces or if you require any further assistance, please don’t hesitate to contact us at [email protected].
We are currently investigating an issue affecting Service Requests for customers in the US and AU regions. Initial findings indicate that when the approval process is configured to use the Incident Assignee as the approver, the workflow may terminate unexpectedly with the following error: “The task [Task Name] has been automatically declined per predefined approval conditions because the approval step contains unknown approvers.” Our engineering teams are actively working to identify the root cause and determine a resolution. If you have questions, are experiencing related issues, or would like to provide additional details, please contact us via chat or email at [email protected]. We will continue to provide updates as more information becomes available.
Our team is actively investigating the issue, which may be related to a recent deployment. We are working to identify the root cause and resolve it, and we will provide updates as more information becomes available. Thank you for your patience.
Our team is continuing to investigate the issue and is focused on identifying the root cause and resolving it as quickly as possible. We will provide updates as new details become available. Thank you for your patience.
We have identified the root cause of the issue affecting Service Request approval workflows for customers in the US and AU regions. We are currently testing a fix. Once testing is complete, we will proceed with deployment and share further updates.
The fix we had in place did not resolve the issue as expected. Our Engineering team has identified and is currently working on a resolution. Our team is preparing for the deployment, which is expected to be completed within the next hour. If this changes, we will provide an update immediately.
This issue has been resolved.
We are currently investigating an issue affecting the Service Desk in the AU Data Center, where newly created objects, such as tickets and assets, are not appearing in the user interface as expected. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. We appreciate your patience and understanding.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently seeing performance slowness within the Service Desk Application, and our team is investigating this matter. This impacts actions such as navigating through the Incidents page and other areas of the app.
The platform performance has greatly improved, and while that is the case, we are still seeing delays, at times, when navigating between pages. The engineering team found a high load on the database, which has been cleared for a couple of hours, and are now focusing efforts on the remaining delay issues. You can expect the next update in one hour.
This issue has been resolved.
We are currently investigating an issue affecting the Service Desk in the AU Data Center. New tickets are not appearing in the UI. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. We appreciate your patience and understanding.
This issue has been resolved.
We are aware of an issue affecting a scheduled Service Desk service catalog item in our EU data center. Our team is actively working to identify the root cause and restore normal functionality. Additional updates will be shared as they become available.
Additional resources have been allocated to help manage the queue. As a result, the backlog is now being processed efficiently, and pending items are getting cleared. Additional updates will be shared as they become available.
Scheduled service catalog item are now being processed. We are monitoring the situation closely to ensure continued stability.
This incident has been resolved.
We are currently investigating an issue affecting Service Desk in EU Data Center. Round-robin assignment and Automation Rules process are delayed, this affects automation assigning and or updating incidents. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. We appreciate your patience and understanding.
We have identified performance degradation in the Service Desk application within EUDC. This issue is impacting multiple functionalities of the application. Our team is actively investigating the issue and working to identify the root cause. Further updates will be shared as more information becomes available.
Service Desk EU data-center degradation issue affecting the application has now been restored. System performance is now normal and the application is operating as expected. We continue to monitor performance closely to ensure ongoing stability and reliability.
This incident has been resolved.
