Updated

This morning, our Technical Team triggered a release containing a database migration to prepare a new important feature. This migration aimed to update our main database.

The migration locked the main database to execute schema and data transformation. For the entire time the migration was running, a transaction lock prevented users from accessing our main database, via API calls, for their own needs. All requests ended up in error.

This migration used a new utility function that was introduced last week to prevent migrations from running more than once (in very rare concurrent cases) but its usage requires further work.

Our Technical Team is currently working on aligning migration practices and documentation for this new utility function. This will prevent similar events in the future.

Thank you for your patience during this incident.