Flatfile experienced a minor incident on August 4, 2025 affecting Platform API and Spaces, lasting 31m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 04, 2025, 07:54 PM UTC
We are currently investigating an issue that is causing some events to fail. We are working to restore this as quickly as possible
- monitoring Aug 04, 2025, 08:17 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Aug 04, 2025, 08:23 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 04, 2025, 08:26 PM UTC
This incident has been resolved.
- postmortem Aug 06, 2025, 03:07 PM UTC
# Incident Overview 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. ## Details of the Incident 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` ## Impact Assessment 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. ## Root Cause 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. ## Resolution 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. ## Security and Data Integrity 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.