Historical record of incidents for Polly
Report: "UK server issues"
Last updateWe are currently investigating an issue between our primary application servers and database servers.
Report: "Unable to start any new containers"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are continuing to work on a fix for this issue.
An issue with one of our suppliers is preventing us from starting any new containers. This is causing major outages for our portals. We are actively monitoring the situation and looking for workarounds.
Report: "Portal delays caused by large decision trees"
Last updateThis incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We have created a fix for this issue which we are now deploying to production.
We have identified an issue where large decision trees + links to other large decision trees are causing high CPU load on the servers. Anyone working on these servers will have degraded performance. We have identified the issue and are working on a fix.
Report: "App component not available"
Last updateBetween ~15:30 and ~15:50 customers experience downtime while working in the App component. A bug combined with 2 specific other factors caused crashing containers. The containers restarted immediately so users could login again after around 10 minutes. After around 20 minutes a hotfix was deployed on production.
Report: "Articles not loading correctly in Portal"
Last updateA bug in the latest portal production code caused an issue where articles didnt load for portal users.
Report: "Helpcenter contactform not working correctly"
Last updateThis incident has been resolved.
Primary fields (email, subject, content) of contactform are rendered correctly again. There is still an issue with the transcript rendering which we are still working on.
The issue has been identified and a fix is being implemented.
Report: "Degraded performance for UK Portal containers"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
Report: "Chromium version 95 is causing article editor to crash"
Last updateWe have implemented a hotfix to solve this issue. Incident is resolved, but bug remains open for further solving.
The issue is caused by the svg icons in the editor. As a hotfix we have temporarily disabled the svg icons while we continue to solve the issue.
We have identified that chromium version 95 is the cause of this issue. A workaround is to not upgrade to chrome (or chromium) v95 and keep using v94 (or downgrade to v94) or to use a non-chromium browser like Firefox. We are currently investigating how we can fix our editor to work with chromium version 94.
Report: "Search API not working correctly"
Last updateThis incident has been resolved.
We are continuing to monitor for any further issues.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
Report: "Newly created articles using elements dont store published content when saved"
Last updateThis issue has been resolved. Element content is now published correctly when saved. To fix any affected articles / elements, simply save the element content 1 time and the content should be visible.
We are currently deploying a fix to our staging environment. After testing we will deploy the fix to production.
We are continuing to work on a fix for this issue.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
Report: "Portal degraded performance"
Last updateThere was degraded portal performance due to some containers running out of memory and crashing.
Report: "Organisation license agent usage overview very slow / not working"
Last updateThis incident has been resolved.
The issue has been identified and a fix is being implemented.
Report: "Database unreachable"
Last updateDatabase unreachable due to heavy workload. This affected all response times in the application.