Notifications
Clear all
Topic starter
I'm trying to invoke a sub-workflow, sourcing the database from a list selection.
However, it consistently returns an "Invalid URL" error.
Interestingly, I can successfully call the sub-workflow using the "Execute Workflow" node.
json
{
"errorMessage": "Invalid URL",
"errorDetails": {
"rawErrorMessage": [
"Invalid URL"
],
"httpCode": "none"
},
"callin.ioDetails": {
"nodeName": "My Open Tasks",
"nodeType": "callin.io/n8n-nodes-langchain.toolWorkflow",
"nodeVersion": 1.2,
"itemIndex": 0,
"runIndex": 0,
"time": "14.11.2024, 01:50:39",
"callin.ioVersion": "1.67.1 (Cloud)",
"binaryDataMode": "filesystem",
"stackTrace": [
"NodeApiError: Invalid URL",
" at RoutingNode.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/RoutingNode.js:183:23)",
" at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:773:23)",
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:704:51",
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1134:20"
]
}
}
Could this be a bug, or am I overlooking something?
Thanks.
Posted : 14/11/2024 12:56 am
It seems your topic is missing some crucial details. Could you please provide the following information, if relevant?
- callin.io version:
- Database (default: SQLite):
- callin.io EXECUTIONS_PROCESS setting (default: own, main):
- Running callin.io via (Docker, npm, callin.io cloud, desktop app):
- Operating system:
Posted : 14/11/2024 12:56 am
Topic starter
I'm encountering an issue with an invalid URL in my workflow. Here are the details:
json
{
"errorMessage": "Invalid URL",
"errorDetails": {
"rawErrorMessage": [
"Invalid URL"
],
"httpCode": "none"
},
"callin.ioDetails": {
"nodeName": "My Open Tasks",
"nodeType": "callin.io/n8n-nodes-langchain.toolWorkflow",
"nodeVersion": 1.2,
"itemIndex": 0,
"runIndex": 0,
"time": "14.11.2024, 01:50:39",
"callin.ioVersion": "1.67.1 (Cloud)",
"binaryDataMode": "filesystem",
"stackTrace": [
"NodeApiError: Invalid URL",
" at RoutingNode.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/RoutingNode.js:183:23)",
" at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:773:23)",
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:704:51",
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1134:20"
]
}
}
Posted : 14/11/2024 10:19 am
Hello,
That's quite unusual. Could you share a screenshot of the error message? It doesn't appear to originate from the execute workflow node, so the issue might be stemming from the workflow you're invoking.
Posted : 14/11/2024 5:50 pm
Topic starter
To rule out personal errors, I copied the Suggest meeting slots using AI | callin.io workflow template.
The same error occurred with the “Workflow Tool” node.
Therefore, I suspect it might be a system error.
Posted : 14/11/2024 10:43 pm
It appears so. I'll test it this morning to see if I can replicate the issue.
Posted : 15/11/2024 6:09 am
Topic starter
Hi there, were you able to reproduce this issue?
Posted : 17/11/2024 8:53 am
Were you able to find a resolution? I'm encountering the identical problem when trying to access a Basic LLM Chain.
Posted : 18/11/2024 1:06 am
Hello,
Not yet, I've experimented with a straightforward workflow on version 1.68 using the example below, and it appears to be functioning.
Could you please test this workflow and attempt an update?
Posted : 20/11/2024 6:05 am
I'm encountering the same problem with a self-hosted setup using Docker.
This is the log output from the docker compose configuration:
n8n-1 | Invalid URL
n8n-1 | TypeError: Invalid URL
n8n-1 | at new URL (node:internal/url:806:29)
n8n-1 | at dispatchHttpRequest (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/adapters/http.js:232:20)
n8n-1 | at /usr/local/lib/node_modules/n8n/node_modules/axios/lib/adapters/http.js:152:5
n8n-1 | at new Promise (<anonymous>)
n8n-1 | at wrapAsync (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/adapters/http.js:132:10)
n8n-1 | at http (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/adapters/http.js:170:10)
n8n-1 | at Axios.dispatchRequest (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/dispatchRequest.js:51:10)
n8n-1 | at processTicksAndRejections (node:internal/process/task_queues:95:5)
n8n-1 | at Axios.request (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/Axios.js:40:14)
n8n-1 | at Object.httpRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:778:18)
n8n-1 | at Axios.request (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/Axios.js:45:41)
n8n-1 | at processTicksAndRejections (node:internal/process/task_queues:95:5)
n8n-1 | at Object.httpRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:778:18)
n8n-1 | at RoutingNode.rawRoutingRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/RoutingNode.js:346:29)
n8n-1 | at RoutingNode.makeRoutingRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/RoutingNode.js:429:28)
n8n-1 | at async Promise.allSettled (index 0)
n8n-1 | at RoutingNode.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/RoutingNode.js:164:35)
n8n-1 | at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:773:23)
n8n-1 | at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:704:51
n8n-1 | at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1134:20
Posted : 25/11/2024 1:21 pm
I'm encountering the same problem with my self-hosted Docker setup. It's been quite frustrating! I'm hoping it's a bug that will be addressed.
I am running: 1.69.2 (Self Hosted)
My error:
Other info
Item Index
0
Run Index
0
Node type
@callin.io/callin.io-nodes-langchain.toolWorkflow
Node version
1.2 (Latest)
callin.io version
1.69.2 (Self Hosted)
Time
03/12/2024, 22:03:12
Stack trace
NodeApiError: Invalid URL at RoutingNode.runNode (/usr/local/lib/node_modules/callin.io/node_modules/callin.io-workflow/dist/RoutingNode.js:183:23) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Workflow.runNode (/usr/local/lib/node_modules/callin.io/node_modules/callin.io-workflow/dist/Workflow.js:773:23) at /usr/local/lib/node_modules/callin.io/node_modules/callin.io-core/dist/WorkflowExecute.js:706:51 at /usr/local/lib/node_modules/callin.io/node_modules/callin.io-core/dist/WorkflowExecute.js:1137:20
Posted : 03/12/2024 9:59 pm
Experiencing the same issue here… I'm using a self-hosted setup. I have two distinct tools configured, both pointing to similar (the same domain) endpoints. It appears the second tool's endpoint isn't functioning correctly. Both endpoints are actively serving other services and are confirmed to be fully operational.
{
"errorMessage": "Invalid URL",
"errorDetails": {
"rawErrorMessage": [
"Invalid URL"
],
"httpCode": "none"
},
"n8nDetails": {
"nodeName": "validateAddressTool",
"nodeType": "@n8n/n8n-nodes-langchain.toolHttpRequest",
"nodeVersion": 1.1,
"itemIndex": 0,
"runIndex": 0,
"time": "12/23/2024, 1:19:50 PM",
"n8nVersion": "1.71.3 (Self Hosted)",
"binaryDataMode": "default",
"stackTrace": [
"NodeApiError: Invalid URL",
" at RoutingNode.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/RoutingNode.js:193:23)",
" at processTicksAndRejections (node:internal/process/task_queues:95:5)",
" at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:792:23)",
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:724:51",
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1155:20"
]
}
}
Posted : 23/12/2024 7:28 pm
Hi, it seems adding an "Edit Fields" node after the Stringify Response Node helped resolve the issue for me. I simply set the field to the output of the preceding node, and the error disappeared. I'm not entirely sure why this works, but perhaps it ensures the previous node completes its execution.
Posted : 01/01/2025 5:10 pm
Still encountering the same error! Running Docker on Digital Ocean. Any insights or potential workarounds?
Posted : 16/01/2025 9:30 pm
Page 1 / 2
Next