502 Bad Gateway – n8n Cloud Workspace Down

Questions
,
1

My n8n workspace is currently inaccessible. After running a workflow that attempted to download a large (~308MB) video file from Google Drive (using the alt=media API method), the instance immediately went down and is now showing a 502 Bad Gateway error.

I can’t access the editor or manage any workflows/executions.

Unfortunately, I’m unable to share the workflow as the workspace cannot be accessed at all due to the 502 error.

The last workflow attempted to:

  • Use HTTP Request node to GET a video file from Google Drive (via https://www.googleapis.com/drive/v3/files/{{fileId}}?alt=media)

Information on your n8n setup

  • n8n version: Cloud (latest, managed by n8n)
  • Database (default: SQLite): Managed by n8n Cloud (unsure)
  • n8n EXECUTIONS_PROCESS setting (default: own, main): Not applicable (cloud-managed)
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n Cloud
  • Operating system: n8n Cloud infrastructure (not self-hosted)

Is there any way to revert the instance to the state before the workflow was triggered?

I’ve already reached out to [email protected] but I wanted to ask here as well in case others have faced this.

Thanks in advance for any guidance!

2

The link you’ve posted is not a proper cloud instance URL. It should be of the format username.app.n8n.cloud. Could you try logging in to the cloud dashboard and try and see if you can access the instance through there?

If the instance is unavailable due to crashing, it will require some intervention from us. If you want, you can privately message me your cloud signup email / username and I can check the instance status.