n8n - 💡(How to fix) Fix [Bug] Notion Trigger node crashes on "Active" but works on "Test Step" (Empty Error Details)

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

The Notion Trigger node (specifically the pagedUpdatedInDatabase event) functions correctly during manual testing (Test Step), but fails immediately when the workflow is set to Active. Crucially, the "Error details" pane is completely empty, showing no status code or error message, which makes debugging impossible. Check the Executions log; the error details are missing/blank. If it fails, the UI must display the actual error returned by the Notion API (e.g., 400, 404, 500) so the user can diagnose the data issue. UI Bug: No error description, stack trace, or API response code is displayed in the error panel.

RAW_BUFFERClick to expand / collapse

Bug Description

<img width="1868" height="916" alt="Image" src="https://github.com/user-attachments/assets/3bd7d7e0-9c8b-4ba7-8d54-eecae5f27644" /> <img width="1861" height="884" alt="Image" src="https://github.com/user-attachments/assets/075d3b99-2cde-4a8c-8d9f-ea742dee8e8b" />

The Notion Trigger node (specifically the pagedUpdatedInDatabase event) functions correctly during manual testing (Test Step), but fails immediately when the workflow is set to Active. Crucially, the "Error details" pane is completely empty, showing no status code or error message, which makes debugging impossible.

To Reproduce

Set up a Notion Trigger node (Page Updated in Database).

Confirm the node works via "Test Step".

Activate the workflow.

The workflow fails on the first polling interval.

Check the Executions log; the error details are missing/blank.

Expected behavior

The trigger should stay active and poll for changes correctly. If it fails, the UI must display the actual error returned by the Notion API (e.g., 400, 404, 500) so the user can diagnose the data issue.

Debug Info

In Test Mode: Works fine, retrieves records.

In Active Mode: Fails instantly.

UI Bug: No error description, stack trace, or API response code is displayed in the error panel.

Operating System

Ubuntu 24.04.4 LTS

n8n Version

2.19.4

Node.js Version

v18.19.1

Database

SQLite (default)

Execution mode

main (default)

Hosting

self hosted

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…

FAQ

Expected behavior

The trigger should stay active and poll for changes correctly. If it fails, the UI must display the actual error returned by the Notion API (e.g., 400, 404, 500) so the user can diagnose the data issue.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING