Critical UI always Offline Issue so cant Publish + lot of Latency since v2.7.0 (Instance: Google Run)

Questions
1

Critical UI always Offline Issue so cant Publish + lot of Latency since v2.7.0 (Instance: Google Run)

Describe the problem/error/question

I’m reaching out to report a significant performance regression starting from version 2.7.0.
The Problem:
In versions 2.5.2 and earlier, my instance worked perfectly runing on Google Run. However, since updating to 2.7.0 (and subsequent versions), the editor UI always shows an “Offline” status.
Symptoms:
Publishing Blocked: Even though the service is technically running, the UI does not allow me to “Publish” or save changes to new workflows while in this offline state.
System Slowdown: The entire interface has become extremely sluggish (laggy), making it difficult to build or edit complex nodes.

n8n setup

  • n8n version: actual 2.5.2
  • Google Cloud Run

n8n setup failed

  • n8n version: 2.8.2 - 2.7. (1,2,3,4 )
  • Google Cloud Run
2

hello @rene_lazalde
It was fixed in 2.7.5. Change the /healthz endpoint to anything else via the N8N_ENDPOINT_HEALTH variable. E.g. N8N_ENDPOINT_HEALTH=health

Upgrading to v2.7.x Causes All Workflow Editing to FAIL as OFFLINE When n8n Runs on Google Cloud Run · Issue #25656 · n8n-io/n8n