Execution fails with no failed nodes

Hi,
We’re having the same issue as reported here running on n8n cloud.

I logged it as a bug but they can’t help. It seems as a platform if a failure is report some result should be available.

The workflow fails, the execution data is removed and no nodes are identified.

How can we move this forward.

Thanks
Dave

instance information

Debug info

core

  • n8nVersion: 1.83.2
  • platform: docker (cloud)
  • nodeJsVersion: 20.18.3
  • database: sqlite
  • executionMode: regular
  • concurrency: 20
  • license: community
  • consumerId: 00000000-0000-0000-0000-000000000000

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 720 hours
  • maxCount: 25000 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/134.0.0.0 safari/537.36
  • isTouchDevice: true

Generated at: 2025-03-19T11:09:50.067Z

The error in the post you linked to happens when he n8n instance crashes in the middle of an execution. Is your n8n instance also crashing?
If not, are you using sub-workflows?

We’re running on n8n cloud. I have no idea if the instance is crashing. I don’t know how we could see that.

We are using sub-workflows but even if the failure is in a sub workflow it normally bubbles up to the main workflow.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.