Fix Notion delivery when it is paused
A rejected connection, an unshared database, a changed property, or five refused leads in a row pauses Notion delivery. Read the reason and resume.
Notion delivery pauses when Notion returns an error that another attempt cannot fix. The Notion page under Integrations in the sidebar (/integrations/notion) then reads “Delivery to Notion is paused” at the top. Needs attention under it shows the reason and, for most reasons, a button that fixes it, with Resume beside it.
Read the pause reason
| Reason | What it means | The fix |
|---|---|---|
Reconnect Notion: it no longer accepts the saved connection. | Notion rejected the connection, and renewing it once did not help. It was removed in Notion or revoked | Reconnect Notion |
Notion can no longer reach this database. Share it with the Embers integration again, or pick another. | The database is no longer shared with Embers | Share it again in Notion, or Pick a database |
Pick a database: the one Embers writes to was deleted or is no longer shared. | Notion cannot find the database | Pick a database |
Re-map Notion fields: a property Embers writes to was deleted or changed type in your database. | A property you mapped is gone or has a new type | Re-map Notion fields |
Notion paused after 5 leads in a row were rejected (last: validation_error). | Five leads in a row were refused, with none delivered in between | Fix the cause, then Resume |
Notion paused after receiving HTTP 404. (or another 4xx) | Notion refused the request for a reason other than one lead’s values | Fix the cause, then Resume |
Notion delivery retries were exhausted. | Rate limits, timeouts, or Notion outages lasted through every retry | Resume once Notion is healthy |
Rate limits and outages are retried instead of paused: the first attempt plus seven more, from 30 seconds out to about 6.3 days, the same schedule as webhook retries. When Notion says how long to wait, Embers waits at least that long.
One lead Notion refuses for its own values does not pause anything. A validation_error, or a lead with no value for the only match key you mapped, fails that delivery on its own and Embers sends the next lead. Only five in a row pause the install. One delivered lead resets the count, and resuming starts it from zero.
Fix and resume
-
Reconnect, or share the database again
For a rejected connection, choose Reconnect Notion and approve Embers on Notion’s consent screen. For a database that is no longer reachable, share it with Embers in Notion, or choose Pick a database and select another.
-
Check the mapping
Reconnecting to the same Notion workspace keeps your database and mapping. Picking a different database clears the mapping, so map its properties again.
-
Test the connection
Send test, beside the status at the top of the page, checks the connection, the database, and the mapped properties without creating a page.
-
Re-map Notion fields
Choose Re-map Notion fields. A row whose property is gone shows Missing in Notion. Pick another property, or choose Not sent, then choose Save mapping. Saving clears the pause.
-
Or restore the property in Notion
Putting the property back with its old type fixes the cause. Then choose Resume.
-
Fix the cause
For refused leads, choose Failed on the Activity card, read the reason on a row, and fix the property or value Notion objected to. For an outage, check Notion’s status page.
-
Choose Resume
Resume appears under Needs attention while delivery is paused. Your event choices, rules, database, and mapping are unchanged by a pause.
Recover the leads you missed
Leads that qualified while Notion was paused were kept as Blocked, not sent. After you resume, choose Retry on a blocked row on the Activity card, or select the leads on the leads list and send them to Notion. A lead already on a page in the current database is skipped as already synced to Notion unless you tick ignore rules, in which case its page is updated rather than duplicated.
Troubleshooting
- The pause returns right after reconnecting. The database is still not shared, or Notion still refuses the connection. Share the database on Notion’s consent screen, then choose Pick a database.
- Resume is missing. Delivery is not paused, or you are not a workspace admin.
- A row says the match key is missing. The lead has no value for the only key you mapped. Map LinkedIn profile URL and Embers ID both, or accept that this lead cannot be matched.
- The Status column is empty. Notion has no option with that name on the property. Add
active,contacted, anddismissedas options, because Embers never adds one.
Send the pause reason and the time to viraj@useembers.com if it does not clear. HubSpot follows the same pause rules: see HubSpot delivery is paused.
Related
Frequently asked questions
- Do I lose my Notion mapping if I reconnect?
- Not when you reconnect to the same Notion workspace: the database and the mapping are kept, and the pause clears. Connecting a different workspace clears both.
- Does a Notion rate limit pause delivery?
- No. Rate limits and outages are retried, honouring the wait Notion asks for, up to seven times over about 6.3 days. Only when every attempt fails does delivery pause.
- Why did one lead fail without pausing anything?
- Notion refused that lead's own values, or the lead had no value for the only match key you mapped. Only five of those in a row pause the install.
Was this article helpful?
What went wrong?
Thank you. We read every answer.
Still stuck?
Send us the article you were following and what happened. We answer from the same inbox that writes these pages.