Hi,
In recent versions, I can not see Execution URL in Error Trigger node anymore
It is rather important for me to link to Execution URL to check error faster.
At old versions, I could get URL of Execution by this json:
{{$node["Error Trigger"].json["execution"]["url"]}}
Could you consider for this feature?
Hey @cmdntd987, sorry to hear you’re having trouble here. I’m still getting the execution URL in the current version 0.153.0 though:
Could you provide an example workflow where the URL is missing for you?
I 'm still in version 0.152.0
This is my node
The response
[
{
"execution": {
"error": {
"name": "NodeOperationError",
"cause": {
},
"node": {
"name": "Add subcriber1",
"type": "n8n-nodes-base.sendy",
"position": [
800,
350
],
"parameters": {
"resource": "subscriber",
"operation": "add",
"email": "={{$node["Set data"].json["email"]}}",
"listId": "1",
"additionalFields": {
"country": "VN",
"name": "={{$node["Set data"].json["type"]}} {{$node["Set data"].json["product"]}} - {{$node["Set data"].json["last_name"]}} {{$node["Set data"].json["name"]}}"
}
},
"credentials": {
"sendyApi": {
"id": "23",
"name": "Sendy API - sendy.working24.net"
}
},
"typeVersion": 1,
"continueOnFail": true,
"alwaysOutputData": true
},
"timestamp": 1639573280212,
"message": "Sendy error response [400]: Already subscribed.",
"stack": "NodeOperationError: Sendy error response [400]: Already subscribed. at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Sendy/Sendy.node.js:138:31) at runMicrotasks (<anonymous>) at processTicksAndRejections (internal/process/task_queues.js:93:5) at async /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/src/WorkflowExecute.js:447:47"
},
"lastNodeExecuted": "Add subcriber1",
"mode": "webhook"
},
"workflow": {
"id": "80",
"name": "Contact lead - Save email list 4.0"
}
}
]
Are you saving the execution data for the affected workflow @cmdntd987? And are you using a specific execution mode by any chance?
I changed to use queue mode and worker
It seems this issue related to this mode of n8n
But I do not know how to check this. Could you help me know how to check this?
So between getting the URL and not getting it anymore you changed to queue mode? If so, you might have been affected by the problem described and fixed here:
Could you try updating to version 0.153.0 and see if the problem still persists for you?
Thanks. I upgraded to 0.153.0
I waiting for next error report. I will reply you later.
It’s ok now. Thanks very much.
Awesome, glad to hear it’s now working again and thanks so much for confirming!