Flexpa - Notice history

This incident has been resolved.

What happened?

An update (migration) to our database took longer than expected and began to saturate connection resources. This resulted in services such as API not being able to make new connections.

What are we doing to remediate?

We are setting up increased monitoring in order to triage database connection issues faster. We are also optimizing our database lookups by using an index on the table that caused the issue.

This incident has been resolved.

This incident has been resolved. We experienced a process failure during a routine database update, which caused some users to encounter errors when accessing the Flexpa API.

Why did it happen?

A database migration did not complete as expected, causing discrepancies between the application and the database. This was primarily due to the migration being prematurely stopped by our automated health checks.

How to prevent it in the future?

We are improving our deployment process to ensure that the application remains in a consistent state, even if a database update does not complete successfully. This change is intended to prevent similar errors from occurring in the future.