> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bulknotion.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> Use this when a run will not start, a job seems stuck, pages failed, or a condition matches nothing.

## A condition matches nothing

<Warning>
  The count says **0 pages** for a condition you expected to catch many.
</Warning>

<Steps>
  <Step title="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.
  </Step>

  <Step title="Check the value exists">
    A select or status condition matches the exact option. `Done` and `done` are
    different values in Notion.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## 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.

<Note>
  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.
</Note>

### "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](/credits#running-out-of-credits).

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

<Warning>
  Progress sits at the same number for a while.
</Warning>

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.

<Steps>
  <Step title="Give it a moment">
    Check again in twenty seconds or so before assuming something is wrong.
  </Step>

  <Step title="Look at History">
    A job that has genuinely failed shows as failed there, with a reason.
  </Step>

  <Step title="Contact support with the job ID">
    If it has been much longer than the size suggests, send us the job ID from
    History.
  </Step>
</Steps>

## 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](/notion-connection#adding-pages-later).
* **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.

Successful pages are already updated. Re-running affects only the pages you
select again.

## A database or template is missing

<Warning>
  The database does not appear in search, or the template list is empty.
</Warning>

Almost always the Notion authorisation. BulkNotion only sees what you selected on
Notion's screen.

<Steps>
  <Step title="Reconnect and widen the selection">
    From **Settings**, run the connection again and tick the database — and the
    page holding the template.
  </Step>

  <Step title="Check the workspace">
    With more than one workspace connected, make sure the switcher is on the one
    holding the database.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## Claude cannot find the tools

Ask it to reconnect the BulkNotion connector. MCP clients cache the tool list, so
a client connected before an update may be working from a stale copy.

More on the connector: [MCP overview](/mcp/overview).

## Still stuck

Contact support with the **job ID** from History if it concerns a specific run.
It is the fastest way for us to see what happened.