502 errors / instance reported as offline when it is not

[ptolomea9]

Describe the problem/error/question

n8n keeps timing out and reporting my instance is offline - I'm updated to the most current version, and the admin panel says my instance is online. n8n loses execution data and says that it can't fetch data against executions that were just live/running

What is the error message (if any)?

Getting 502 errors / instance offline. A lot of intermittent timeouts.

Please share your workflow/screenshots/recording

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.

Share the output returned by the last node

Debug info

core

• n8nVersion: 2.7.1
• platform: docker (cloud)
• nodeJsVersion: 22.22.0
• nodeEnv: production
• database: sqlite
• executionMode: regular
• concurrency: 20
• license: enterprise (sandbox)

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/144.0.0.0 safari/537.36
• isTouchDevice: false

Generated at: 2026-02-03T18:54:16.629Z}

[n8n-assistant]

Hey @ptolomea9,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-6653".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

---

For INTERNAL use only: GHC-6653