Notion API validation error: Unsaved transactions with unrecognized error message

Other Questions Notion
1

I’m getting a strange error when trying to add data to my Notion database through the API. Everything was working fine before but now I keep getting this error message:

response: {
  object: 'error',
  status: 400,
  code: 'validation_error', 
  message: 'Unsaved transactions: Unrecognized error.'
}

I was working on some code to save form data when users navigate away from the page. After making those changes, I started getting validation errors. Even though I reverted all my changes back to the working version, rebuilt everything, and restarted my server, the same error keeps happening.

The weird part is that this same code was creating database entries successfully just yesterday. Now, even the old working code throws this error. Has anyone seen this before or know what might cause unsaved transactions in Notion API?

2

I hit this exact error last month during a batch import. Turned out to be concurrent API requests hitting the same database at once. Even though you reverted your code, background processes or multiple instances might still be sending conflicting requests. Check your rate limiting and make sure you’re not exceeding Notion’s API limits. I fixed it by adding small delays between requests and proper error handling for 429 responses. The “unsaved transactions” thing means Notion’s backend can’t handle overlapping database changes, so try reducing concurrency.

3

This sounds like a database state issue on Notion’s end, not your code. I ran into something similar a few months ago - my integration was working fine, then suddenly started throwing weird validation errors. The “unsaved transactions” error usually means Notion’s internal database operations are getting stuck or conflicting. Since reverting your code didn’t help, check if your database properties were modified recently or if any automation rules got added. Sometimes clearing your API auth and regenerating the integration token helps reset whatever’s causing the conflict. Also worth checking Notion’s status page to see if there are any ongoing API issues.

4

Same thing happened to me! Check for webhooks or automations running in the background - they might be triggering API calls you can’t see. Notion gets confused when there’s multiple writes happening at once. Also check your database permissions. I’ve seen this error when the integration token loses write access. If nothing else works, restart your Notion workspace - that fixed it for me once.