At 2pm UTC time, we've deployed a new version of our V2 product and executed changes to the database in order to optimize the stored data. However, while doing so, we've triggered a a heavy process that caused tables related to our schedule feature to not respond in a timely manner and thus impacting the platform. We've immediately proceeded to stop that process and recover functionality in a matter of minutes.

Moving forward, we will put in place checks to prevent these processes from being executed in bulk and test the impact during the pre-deployment phase.

Since data processing services are in isolation, all agent and ticket activity was collected and processed normally.