n8n - 💡(How to fix) Fix Supabase node throws "Invalid URL" in appendResumeToken on v2.16.2 (regression) [2 comments, 2 participants]

{ "errorMessage": "Invalid URL", "n8nDetails": { "n8nVersion": "2.16.2 (Self Hosted)", "binaryDataMode": "filesystem", "stackTrace": [ "TypeError: Invalid URL", " at new URL (node:internal/url:819:25)", " at appendResumeToken (.../n8n-core/src/execution-engine/node-execution-context/utils/get-additional-keys.ts:14:17)", " at getAdditionalKeys (.../get-additional-keys.ts:30:15)", " at ExecuteContext.get additionalKeys (.../node-execution-context.ts:435:27)", " at ExecuteContext._getNodeParameter (.../node-execution-context.ts:473:11)", " at ExecuteContext.getNodeParameter (.../execute-context.ts:136:9)", " at ExecuteContext.execute (.../Supabase/Supabase.node.ts:174:25)", " at WorkflowExecute.executeNode (.../workflow-execute.ts:1045:31)", " at WorkflowExecute.runNode (.../workflow-execute.ts:1224:22)" ] } }

TL;DR

The Invalid URL error in the Supabase node after upgrading to n8n 2.16.2 is likely due to an issue with the appendResumeToken function, suggesting a regression similar to the one reported for the Google Sheets node.

Guidance

• Verify that the Supabase credential is correctly configured and the instance is reachable via HTTPS, as the error might be related to URL construction.
• Check if downgrading to a previous version of n8n (e.g., 2.15.x) resolves the issue, to confirm if it's a regression introduced in 2.16.2.
• Investigate the appendResumeToken function in the n8n-core package to see if there are any changes or issues related to URL handling that could be causing the error.
• Consider reaching out to the n8n community or developers, referencing the similar issue with the Google Sheets node, to see if there's a known fix or workaround.

Example

No specific code example is provided due to the lack of direct code reference in the issue, but investigating the appendResumeToken function and its usage in the Supabase node could yield insights.

Notes

The issue seems to be related to a regression in n8n 2.16.2, affecting multiple nodes that use the appendResumeToken function. Without direct access to the code or more specific details about the changes in 2.16.2, it's challenging to provide a precise fix.

Recommendation

Apply a workaround by downgrading to a previous version of n8n (if possible) until the issue is officially addressed, as it seems to be a regression introduced in version 2.16.2.