Notion Node Bug: The relation id "fffbfe90567a-8132-b56d-c3acc1e8eb71" is not a valid uuid with optional dashes

[MJTD]

We’re experiencing this issue on previously working nodes as of 5pm Monday, September 16 at 5pm CDT. We’re using n8n cloud; saw the issue on stable (1.56.2, then 1.58.2), and also on latest beta (1.59.2).

[roNn23]

I’ve put several hours into changing our workflows and I’m not getting anywhere because unfortunately some things that work in the Notion nodes don’t work in the HTTP request. It’s a shame that nobody responds here. We pay a lot of money for the cloud versions and now we are just fixing bugs because the versions don’t work together. And nobody seems to be interested in the problems. In my eyes, that’s not right at all. Where can we escalate such major bugs?

@jan

[jan]

New version [email protected] got released which includes the GitHub PR 10860.

[roNn23]

Thanks @jan – wasn’t aware that there are already devs working on it.

[justincheu]

I am getting a new bug because of the fix.
{
“errorMessage”: “ERROR: Parent Page parameter’s value is invalid. This is likely because the URL entered is incorrect”,
“errorDetails”: {},
“n8nDetails”: {
“nodeName”: “Create Company Research”,
“nodeType”: “n8n-nodes-base.notion”,
“nodeVersion”: 2.2,
“resource”: “page”,
“operation”: “create”,
“itemIndex”: 0,
“time”: “9/20/2024, 11:19:39 AM”,
“n8nVersion”: “1.59.3 (Self Hosted)”,
“binaryDataMode”: “default”,
“stackTrace”: [
“NodeOperationError: ERROR: Parent Page parameter’s value is invalid. This is likely because the URL entered is incorrect”,
" at extractValue (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/ExtractValue.js:132:15)“,
" at getNodeParameter (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:1637:54)”,
" at Object.getNodeParameter (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:2344:24)“,
" at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Notion/v2/NotionV2.node.js:517:90)”,
" at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:722:42)“,
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:670:66”,
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1100:20"
]
}
}

[peter_brueck]

I can confirm this. Upgraded to 1.59.3 (Self Hosted) and still receive the error
ERROR: Parent Page parameter’s value is invalid. This is likely because the URL entered is incorrect

which was reported before (see here).

[netroy]

@justincheu @peter_brueck Can either of you please share the URL you are seeing this error for?

[peter_brueck]

So the (dynamic) ID I want to fetch for is
10a65c10-79bc-808e-9c70-eefeb2f2169d which is a PAGE in Notion.

My node:

My error message:

{
  "errorMessage": "ERROR: Block parameter's value is invalid. This is likely because the URL entered is incorrect",
  "errorDetails": {},
  "n8nDetails": {
    "nodeName": "get_project_blocks",
    "nodeType": "n8n-nodes-base.notion",
    "nodeVersion": 2.1,
    "resource": "block",
    "operation": "getAll",
    "itemIndex": 0,
    "time": "9/23/2024, 1:20:58 PM",
    "n8nVersion": "1.59.3 (Self Hosted)",
    "binaryDataMode": "default",
    "stackTrace": [
      "NodeOperationError: ERROR: Block parameter's value is invalid. This is likely because the URL entered is incorrect",
      "    at extractValue (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/ExtractValue.js:132:15)",
      "    at getNodeParameter (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:1637:54)",
      "    at Object.getNodeParameter (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:2344:24)",
      "    at Object.extractBlockId (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Notion/shared/GenericFunctions.js:983:38)",
      "    at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Notion/v2/NotionV2.node.js:58:75)",
      "    at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:722:42)",
      "    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:670:66",
      "    at processTicksAndRejections (node:internal/process/task_queues:95:5)",
      "    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1100:20"
    ]
  }
}

Let me know if you need any other info!
Best,
Peter

[Laurent_H]

I had the same uuid problem, but after updating to version 1.59.4, everything seems to be back to normal.

[peter_brueck]

Just tried again, also with 1.59.4 the issue persists for me at least

[netroy]

We added another fix for notion’s non-standard UUID usage. It was merged yesterday, and will go out in today’s release.

[jan]

New version [email protected] got released which includes the GitHub PR 10938.