A condition matches nothing
1
Check the property is on the right data source
A database with several data sources has different properties on each. Pick
the data source you mean, then rebuild the condition from the properties it
offers.
2
Check the value exists
A select or status condition matches the exact option.
Done and done are
different values in Notion.3
Invert it to sanity-check
Flip the condition —
is not empty instead of is empty, checked instead of
unchecked. If both directions return 0 out of a database you know has pages,
the condition is not being read the way you intend; simplify to one property
and build back up.A run will not start
”Another job is still running”
Runs started from Claude wait for each other: one at a time per account, so two cannot collide on the same pages. Wait for the current one to finish (History shows its progress), then ask again. Nothing was charged for the refused attempt.The console does not hold you back this way. If you start a second run there
while one is going, both proceed — so give an in-flight run time to finish before
launching another over the same pages.
”Not enough credits”
The run needs more credits than you have, so it was refused before touching anything. Narrow the condition, add a booster, or wait for the monthly refill — see Credits and plans. Retrying will not change the outcome.”The count has changed”
Pages were added to or removed from the database between previewing the run and starting it. Rather than run over a set you have not seen, BulkNotion refuses and asks you to look again. Preview once more, check the new number, and start it.A job seems stuck
Progress moves in batches, not page by page, so it will pause and then jump. Roughly four to six pages a second is normal — a thousand-page run takes a few minutes.1
Give it a moment
Check again in twenty seconds or so before assuming something is wrong.
2
Look at History
A job that has genuinely failed shows as failed there, with a reason.
3
Contact support with the job ID
If it has been much longer than the size suggests, send us the job ID from
History.
Some pages failed
The job reports how many pages failed alongside how many succeeded. Common causes:- BulkNotion cannot reach the page. It was not included when you authorised Notion, or it has since moved. Reconnect and include it — Connecting Notion.
- The page was deleted between the run starting and reaching it.
- Notion was rate-limiting. Large runs occasionally hit this; re-running for the failed pages usually works.
A database or template is missing
Almost always the Notion authorisation. BulkNotion only sees what you selected on Notion’s screen.1
Reconnect and widen the selection
From Settings, run the connection again and tick the database — and the
page holding the template.
2
Check the workspace
With more than one workspace connected, make sure the switcher is on the one
holding the database.
3
Check the template exists in Notion
The template list comes from templates defined on that database in Notion. If
there are none, create one there first.