We're consistently working to evolve Vero's underlying infrastructure to make the platform more efficient and secure.
At the end of March we made some changes to the core database powering "event property" conditions. As a result of this change a series of maintenance tasks failed between March 26th and March 31st. As a result, at March 31st at 4:27am UTC we began observing delays with newsletter and segment calculations that relied on the event data property condition.
We subsequently diagnosed the root cause of the database performance degradation and fixed and reinstated the maintenance operations. As a significant amount of data had accumulated during the intervening period we had to balance running new processing for segment calculations and the maintenance operations which needed to catch up on the data that had not been processed since the incident first occurred.
We saw some gradual improvements as the maintenance progressed and, since this process fully completed (April 11th, 2:35pm UTC), we have seen segment calculations return to nominal performance.
As part of the (unrelated) scheduled maintenance operations that also took place over the weekend of April 10th and 11th we were able to make changes to the processing system that will prevent this occurring again.
We are adding further monitoring to ensure any future issues would be detected more promptly.
If you have any questions, please contact us at email@example.com.