Summary: On January 28th, we deployed a new release for VusionCloud. Due to a planning error, the maintenance was triggered automatically one hour earlier than scheduled. However, the actual maintenance operations began at the usual time of 8:00 AM UTC.
In addition, due to an unexpected data volume to process after server updates, the maintenance continued to have an impact outside of the scheduled hours and caused delays in ESLs synchronization.
On behalf of all Vusion Team we would like to apologise for the inconvenience and concerns it has caused.
Details: The infrastructure updates required a longer than usual downtime for the transmission servers. Despite this, the downtime remained within the maintenance window.
Maintenance operations concluded at 11:30 AM UTC. These operations included monitoring and health checks, such as image transmissions and data ingestion, ensuring that all operations in stores functioned normally. The maintenance was then officially closed.
Impact: The updates generated a significant volume of data that needed to be processed by our systems. This influx of data caused a desynchronization between the backend and the information displayed in Vusion Manager and the API. The delay was resolved after 2:00 PM UTC.
Conclusion: While the maintenance was completed within the designated window and all store operations continued without interruption, the unexpected data volume led to temporary desynchronization issues. These were resolved by 2:00 PM UTC, and normal operations resumed.