A database schema change on the US region Platform introduced a critical issue that blocked the creation of new Spaces. The issue stemmed from a recent migration that altered the structure of a database table, causing downstream errors during insert operations.
At approximately 01:45 MST on August 4th, multiple users began reporting failures when performing file mappings or creating new Spaces via the Platform. The error stemmed from a recent database schema change to our events table.
Attempts to create a Space resulted in a 400 response with the following error
Failed to create new space. Please try again
The incident impacted all users attempting to create new mappings or Spaces on the US region Platform.
Existing Spaces and their associated functionality were unaffected and continued to operate as expected.
The failure was caused by a database migration that altered the structure of database table column used on space creation. Specifically, the change introduced a type mismatch for the column in the table, leading to query execution failures during record creation.
The Flatfile engineering team identified and reverted the trigger logic responsible for incorrectly writing data to the table. Once reverted, Space creation operations on the Platform resumed normal functionality.
This incident did not compromise data security or integrity. All failed writes were blocked by the database’s validation layer, and no corrupt or partial data was written.