Notion API validation error: Unsaved transactions with unrecognized error message

Other Questions Notion
1

Hey everyone, I’m pretty new to working with Notion’s API and I’m stuck on this weird issue.

I have a Node.js application that sends requests to the Notion API for adding new entries to a database. Everything was working fine until yesterday. The records were being created properly and I could see them in my Notion workspace.

I was trying to add some functionality to save data when users navigate away from the page. During testing, I ran into some validation issues which I thought I had resolved. But then this error started appearing:

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

I used git stash to remove all my recent changes and went back to the version that was working before. I rebuilt everything, restarted my server, and refreshed the browser. But the same error keeps happening.

Has anyone encountered this before? What could be causing this issue to persist even after reverting the code?

2

I hit this same issue with a dashboard that updates multiple Notion pages. Turns out it’s how Notion handles database schema changes internally. Even though you reverted your code, if you added new properties or changed existing ones during testing, Notion might still be processing those changes in the background. This causes the validation error because the API validates against a schema that’s still changing. Check your database properties in the Notion UI for any pending changes or corrupted property definitions. I had to completely recreate one of my database properties to fix it. Also check if other apps or integrations are hitting the same database - that could cause conflicts too.

3

This sounds like a server-side state issue, not your code. I’ve hit this before when my app was hammering Notion’s API with concurrent requests during fast user interactions. The “unsaved transactions” error means Notion’s backend is tracking incomplete operations that got cut off. Check your app logs for requests that timed out or got aborted. Even though you rolled back your code, those partial transactions might still be messing with new requests. I usually wait 10-15 minutes before trying again - Notion cleans up stale transactions automatically. You should also add proper request cancellation to prevent this mess next time.

4

it could be a caching issue with the nothin API. try clearing your integration token and make a new one. sometimes, the API hangs on to old states with transactions. also, see if any requests are pending that didn’t finish right. those can still mess things up even if you rolled back.