Duration:
25th May 2023
Initial customer ticket raised 10:42 (UTC)
Incident status notification raised 10:55 (UTC)
Fix released and incident moved to monitoring stage 15:10 (UTC)
Incident status page marked as fully resolved 16:11 (UTC)
Impact: A small number of customers noted an intermittent issue logging into Vivantio. Some of the customers who raised tickets to us, found that once they were in the system, they could maintain access whilst a few experienced issues logging in throughout the incident period.
Cause: After investigation by the Vivantio engineering team, the cause of the issue was determined to be due to a database change being made in preparation for an upcoming release. This database change conflicted with a configuration of the Vivantio Classic UI on one of our web servers, the Vivantio FLEX UI was unaffected but there is a dependency between the login page of the two user interfaces which caused some FLEX UI users being unable to login.
Resolution: Our engineers performed an extensive investigation into the issue and once the root cause was established, they rolled back the database change which corrected the issue. The Vivantio QA team tested the system fully before we updated the incident status page and continued to monitor the system for a subsequent period of time.
The Engineers will continue to evaluate the cause and will take all findings into consideration for future enhancements and releases and improvements to our QA procedures. All of our platforms are being fully reviewed for configuration issues across both the Classic and FLEX user interfaces to ensure this does not happen again in the future.