In 11.0.9.version we released an improvement for memory handling to be able to scale workload in a more efficient way. This was tested in our test environments but no issues were found.
After releasing 11.0.9. we monitored the solution and noticed that the application servers were not performing as expected and processes were taking too long to complete and were timing out.
Very soon we concluded on the root cause and decided to release a patch version which fixed the issue.
We will add a mechanism to prevent processes to run too long on the servers and to prevent integrations to trigger the same process again in case we have a similar issue. This will stop the problem from escalating.
We have also agreed on a process that should be followed with similar changes so that we are more aware of the risk and are able to notice it earlier in the development process.
Posted Aug 28, 2026 - 11:48 CEST
Resolved
This incident has been resolved.
Posted Aug 26, 2026 - 13:51 CEST
Monitoring
A fix has been implemented and we are monitoring the results.
Posted Aug 26, 2026 - 13:04 CEST
Update
Fix has been verified and will be deployed to production in 15 minutes.
Posted Aug 26, 2026 - 12:58 CEST
Update
We are implementing a fix at the moment. Estimated time to production is 2 hours.
Posted Aug 26, 2026 - 10:32 CEST
Update
We are continuing to work on a fix for this issue.
Posted Aug 26, 2026 - 09:52 CEST
Update
We are continuing to work on a fix for this issue.
Posted Aug 26, 2026 - 09:52 CEST
Identified
We see degraded performance on UI and API. Also on Visma Approval is affected.
Posted Aug 26, 2026 - 09:51 CEST
Investigating
We are currently investigating this issue.
Posted Aug 26, 2026 - 09:30 CEST
This incident affected: Visma Net (Visma Net, Visma Net API).