n8n - 💡(How to fix) Fix Notion Trigger errors silently on every poll that returns no updated pages

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Describe the problem/error/question

Polls that find zero updated pages → marked as error, with startedAt: null, executionTime: 0, and an empty error object (error: {}). The execution never actually starts on the worker. Because errorWorkflow is configured, every failed poll triggers the error handler, generating a Slack DM every minute saying "Error: No error message" — because the error object passed to the Error Trigger is genuinely empty. Toggling Simple from true → false (works for the data shape, but doesn't change the error pattern). Deactivating the workflow, waiting, and reactivating it (re-registered the poller — the failure time shifted from xx:02 to xx:05 of each minute, but the error pattern is identical).

What is the error message (if any)?

No error message. The error object on the parent execution is empty {}, and when delivered to the Error Trigger of the errorWorkflow, the payload looks like: "trigger": { "error": {}, "mode": "trigger" }, On the parent execution itself: startedAt: null, executionTime: 0, error: {}, lastNodeExecuted: "Notion Trigger". "error": {},

  • error: all

Root Cause

Polls that find updated pages in the Notion DB → execute successfully and pass items downstream. Polls that find zero updated pages → marked as error, with startedAt: null, executionTime: 0, and an empty error object (error: {}). The execution never actually starts on the worker. Because errorWorkflow is configured, every failed poll triggers the error handler, generating a Slack DM every minute saying "Error: No error message" — because the error object passed to the Error Trigger is genuinely empty.

RAW_BUFFERClick to expand / collapse

Describe the problem/error/question

The Notion Trigger node (v1, pageUpdatedInDatabase event, poll interval: Every Minute) marks ~95% of its polling executions as errored, even though the workflow is configured correctly and the same trigger runs successfully when executed manually or when there are actually new updated pages to return.

The pattern is consistent and reproducible:

Polls that find updated pages in the Notion DB → execute successfully and pass items downstream. Polls that find zero updated pages → marked as error, with startedAt: null, executionTime: 0, and an empty error object (error: {}). The execution never actually starts on the worker. Because errorWorkflow is configured, every failed poll triggers the error handler, generating a Slack DM every minute saying "Error: No error message" — because the error object passed to the Error Trigger is genuinely empty.

Things I've already tried that did not fix it:

Toggling Simple from true → false (works for the data shape, but doesn't change the error pattern). Disabling Retry on Fail on the trigger. Deactivating the workflow, waiting, and reactivating it (re-registered the poller — the failure time shifted from xx:02 to xx:05 of each minute, but the error pattern is identical).

What is the error message (if any)?

No error message. The error object on the parent execution is empty {}, and when delivered to the Error Trigger of the errorWorkflow, the payload looks like: json{ "trigger": { "error": {}, "mode": "trigger" }, "workflow": { "id": "oPWFaBXEJxv5ndg6", "name": "Notion updates to Slack" } } On the parent execution itself: startedAt: null, executionTime: 0, error: {}, lastNodeExecuted: "Notion Trigger".

Please share your workflow/screenshots/recording

Workflow ID: oPWFaBXEJxv5ndg6 Example failing execution IDs: 21948 (11:32:17 UTC), 21940 (11:30:05 UTC), 21937 (11:29:05 UTC), 21935 (11:28:05 UTC) — all on 2026-05-17. Example successful trigger execution IDs (same workflow, same period): 21946 (11:31:45 UTC), 21932 (11:26:46 UTC) — these found updated pages.

Share the output returned by the last node

"Notion Trigger": [{ "startTime": 0, "executionIndex": 0, "executionTime": 0, "error": {}, "source": [] }]

Debug info

core

  • n8nVersion: 2.20.7
  • platform: docker (cloud)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: 50
  • license: enterprise (sandbox)

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 720 hours
  • maxCount: 25000 executions

client

  • userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-05-17T11:34:38.905Z

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

n8n - 💡(How to fix) Fix Notion Trigger errors silently on every poll that returns no updated pages