n8n - 💡(How to fix) Fix n8n Cloud executions page causes instance to go offline with 502 error

Describe the problem/error/question

I am experiencing a potential bug on my paid n8n Cloud subscription.

This is not a self-hosted Docker installation. I am using n8n Cloud.

When I open a specific workflow and go to the Executions tab, the n8n Cloud instance immediately appears to go offline.

The editor shows the warning:

No network connection. Workflow changes will be saved once the connection is restored.

At the same time, the executions panel fails to load and the UI shows a toast error saying that the execution could not be loaded.

The issue seems related to loading the execution details, not to manually running the workflow from the editor.

When I try to inspect this specific execution, the UI becomes unavailable/offline and the execution details never load.

The issue persists on both:

• n8n stable version 2.21.7
• n8n beta version 2.22.3

I installed the beta version only to test whether the issue was related to the specific n8n version, but the same behavior still occurs.

I am not sharing the real workflow name publicly because it may reveal internal production logic, internal naming, credentials, or business information.

I can provide the workflow name, workflow ID, execution ID, and any additional account-specific details privately to the n8n Cloud support team if needed.

What is the error message (if any)?

The UI shows this toast error:

Problem loading execution
Request failed with status code 502

The editor also shows:

No network connection.
Workflow changes will be saved once the connection is restored.

Please share your workflow/screenshots/recording

I attached screenshots showing:

1. The workflow executions page stuck while loading a failed execution.
2. The n8n editor showing the instance as offline.
3. The toast error with status code 502.
4. The GitHub issue page with the debug information generated by n8n.

I am not sharing the full workflow or the real workflow name publicly because they may contain sensitive production logic, internal naming, credentials, or business information.

The affected workflow and execution details can be shared privately with the n8n Cloud support team if needed.

Please let me know whether n8n Cloud support can inspect the affected execution server-side from my Cloud account, and whether explicit consent or a private support ticket is required.

Steps to reproduce:

1. Open the affected workflow in n8n Cloud.
2. Go to the Executions tab.
3. Select/open the failed execution.
4. The execution details do not load.
5. The instance immediately appears offline in the UI.
6. A 502 error is shown.

Share the output returned by the last node

Not available at the moment because the execution detail page does not load successfully.

Debug info

The following debug information was generated by n8n.

Please note: although the generated debug info reports platform: docker (cloud), this is an n8n Cloud subscription, not a self-hosted Docker installation.

core

• n8nVersion: 2.21.7
• platform: docker (cloud)
• nodeJsVersion: 24.15.0
• nodeEnv: production
• database: sqlite
• executionMode: regular
• concurrency: 5
• license: enterprise (sandbox)

storage

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

pruning

• enabled: true
• maxAge: 168 hours
• maxCount: 2500 executions

client

• userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36
• isTouchDevice: false

Generated at: 2026-05-26T07:25:51.124Z

Additional context

This looks like a server-side or execution-loading issue rather than a normal workflow error, because the n8n Cloud UI itself loses connection and returns a 502 while attempting to load the execution.

It may be related to the size, duration, binary data, or stored execution payload of the failed execution, since the specific failed execution ran for more than 8 hours before failing.

The same issue happens on both the stable version 2.21.7 and the beta version 2.22.3, so it does not appear to be fixed by switching n8n versions.

This is happening on an n8n Cloud subscription, not on a self-hosted Docker instance.

Please let me know if there is a safe way to export or inspect this execution without exposing credentials or sensitive workflow data.