Topdesk Status

Dear Customer, Over the weekend no further issues have been observed and all services have been operating normally. We therefor close the major. The root cause of this disruption has been identified and a Root Cause Analysis will be posted as soon as this becomes available. We sincerely apologize for any inconvenience this issue may have caused and appreciate your patience while we worked to resolve it. Kind regards, The TOPdesk Team

The issue has been resolved, and all affected services are operating normally again. Thank you for your patience and understanding. If you have any questions, our Support team is happy to help.

Dear customer, The issue where some incidents with empty action fields cannot be saved has been fixed. The fixed version is 16.06.007 and has been released to all customer environments. This issue will be thoroughly evaluated to prevent these issues in the future. Our apologies for the inconvenience and thank you for you patience.

Dear customer, The issue where "broken images" in incidents action fields prevent you from saving the incident card has been fixed by development. The version for this fix is 16.06.008. A work around is available for this bug. Work around: ⒈Locate the broken images in the action fields of the progress trail. The broken image will look like a square box with a border around it. ⒉Delete the broken images ⒊Submit the correcte action field ⒋Repeat if more action fields are affected ⒌Save the card Our apologies for the inconvenience. At the time of writing the fix is part of our release cycle.  We cannot yet say when exactly the release will be available. Expected release is by the end of week 25.

The access to my.topdesk has been restored. The issues caused by the maintenance on the 6th-7th of June have been resolved. The cause will be evaluated to prevent similar issues in the future. We apologize again for any inconvenience and thank you for your patience.

The Azure-managed load balancer unexpectedly removed two port rules due to an azure internal issue in the integration between Kubernetes and Azure’s load balancer management. This resulted in a temporary loss of connectivity for our services. Adding the rules by hand resolved the issue. We are currently investigating how to prevent similar future outages.

Dear Customers, As communicated last week, a fix for the Adobe Plugin issue has been released. Due to the TOPdesk release cycle, it took some time to ensure that all environments were updated to the required version. We are pleased to confirm that version 16.06.004 has now been deployed to all TOPdesk environments. This update resolves the issue that prevented operators from logging in when the Adobe Plugin was enabled. You may now safely re-enable the Adobe Plugin. We sincerely apologize for any inconvenience this issue may have caused and appreciate your patience while we worked to resolve it. Kind regards, The TOPdesk Team

We have continued to monitor the import services following the reported issues and have not observed any further occurrences. Everything is operating as expected. As no additional problems have been identified, we will proceed with closing this major.

As no further issues arose during the monitoring period, we are hereby closing the major and all linked incidents. At this time, the exact root cause has not yet been fully identified. Our team will continue to investigate to determine the underlying issue and prevent recurrence. Should you experience any further problems, please do not hesitate to contact us. A RCA will be published once ready.

The issue has been identified and resolved. You can now log in to MyTOPdesk again. We are keeping a close eye on the situation. We apologise for the inconvenience.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.