Notion watch database items triggered although no changes to Notion was made

My scenario is triggering much mor operations than expected (which requires me to by a paid plan)

I’m replicating a notion database into another notion databse. The scenario uses the “watch database items” to detect any changes to the “mother” DB.

I had the scenario run at night time and in the morning my free plan was maxes out.

Has someone encountered the same issue? and found a workaround? I realize the issue may be on Notion’s side.


Welcome to the Make community!

You should be able to go to the scenario history and see what caused your scenario to trigger.

By the way, I do not recommend using Notion as your database, because Notion was originall made as a document editor, and “databases” are a poorly-thought out feature.