Overall, I love this product! I self-host so this may be on my Google Cloud setup, but after working with n8n for about 6-months now I wanted to report back my #1 frustration with it - errors that don’t indicate what caused the error.
I’m not sure if I’m alone here, but on complex workflows, I often times get an error on the execution, but when I open it up no nodes are red or indicate where the error took place. It’s incredibly frustrating as it doesn’t allow me to troubleshoot the error.
I’ve struggled with how to work this over the weeks and months, but I think it’s isolated to when the server may be overloaded or something… but I’m really not sure because I don’t get any of those errors in n8n obviously.
Has anyone else experienced this? I’m self-hosted on GCP using Kubernetes Instance. # Debug info
core
- n8nVersion: 1.91.3
- platform: docker (self-hosted)
- nodeJsVersion: 20.19.0
- database: postgres
- executionMode: regular
- concurrency: -1
- license: enterprise (production)
storage
- success: all
- error: all
- progress: false
- manual: true
- binaryMode: memory
pruning
- enabled: true
- maxAge: 336 hours
- maxCount: 10000 executions
client
- userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/136.0.0.0 safari/537.36
- isTouchDevice: false
Generated at: 2025-05-21T03:28:10.734Z