Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix CRITICAL: Workflow stuck in "Active" state / HTTP 524 on Deactivation – Instance: jcbinetti.app.n8n.cloud [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#28169•Fetched 2026-04-09 08:16:16
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
jcbinettijcbinetti
Participants
jcbinettijcbinettin8n-assistant[bot]n8n-assistant[bot]
Timeline (top)
commented ×1labeled ×1mentioned ×1subscribed ×1

Error Message

Describe the problem/error/question

I am unable to deactivate, archive, or delete a specific workflow in my n8n Cloud instance. Every attempt to change the workflow's state (via UI or REST API) results in an HTTP 524 (Origin Timeout) error after approximately 60 seconds.

What is the error message (if any)?

  • error: all
RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

Describe the problem/error/question

I am unable to deactivate, archive, or delete a specific workflow in my n8n Cloud instance. Every attempt to change the workflow's state (via UI or REST API) results in an HTTP 524 (Origin Timeout) error after approximately 60 seconds. There is a clear inconsistency: The UI shows a "Publish" button (suggesting it's inactive), but the internal state and API responses still report active: true. This "stuck" workflow is currently in conflict with my new production workflow (both accessing the same IMAP mailbox), blocking all further development and testing. Workflow Details: Name: TGV Workflow A v10.8 ID: tnyqUAQX0LlsI6dg URL: https://jcbinetti.app.n8n.cloud/workflow/tnyqUAQX0LlsI6dg Time of occurrence: 2026-04-07 18:25 CEST (2026-04-07 16:25 UTC ) Requested Action: Please perform a force-deactivation or manual deletion of workflow tnyqUAQX0LlsI6dg on the database/server level and restart the affected worker process if necessary to clear any hanging IMAP connections.

What is the error message (if any)?

"Workflow could not be deactivated: Request failed with status code 524" "Problem archiving workflow: Request failed with status code 524"

Please share your workflow/screenshots/recording

<img width="2541" height="1179" alt="Image" src="https://github.com/user-attachments/assets/5ff46b1d-f415-4e4d-8794-6e942ced7524" /> <img width="832" height="507" alt="Image" src="https://github.com/user-attachments/assets/1df43e0b-f67f-4a57-83b9-f46f72275277" />

(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.


The code for all nodes is longer taht the max caracters accepted in this mail form.  
What do you need exacly? 

## Share the output returned by the last node
<!-- If you need help with data transformations, please also share your expected output. -->

The workflow is stuck in an active state and does not produce new execution outputs for the deactivation command, as the Origin server (n8n backend) fails to respond within the Cloudflare timeout window (HTTP 524).

## Debug info

### core

- n8nVersion: 2.13.3
- platform: docker (cloud)
- nodeJsVersion: 24.13.1
- 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 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/146.0.0.0 safari/537.36 edg/146.0.0.0
- isTouchDevice: false
- Login Email: [[email protected]](mailto:[email protected])
- Instance: jcbinetti.app.n8n.cloud

Generated at: 2026-04-07T16:21:15.631Z

extent analysis

TL;DR

The most likely fix is to manually delete the stuck workflow from the database/server level and restart the affected worker process to clear any hanging IMAP connections.

Guidance

  • Investigate the database to understand why the workflow is stuck in an active state despite the UI showing a "Publish" button, suggesting it's inactive.
  • Verify the workflow's internal state and API responses to confirm the inconsistency.
  • Consider reaching out to n8n support for assistance with manually deleting the workflow from the database/server level, as this requires direct access to the backend.
  • After deletion, restart the affected worker process to ensure any hanging IMAP connections are cleared.

Example

No code snippet is provided as the issue does not involve a specific code problem but rather a workflow management issue within the n8n Cloud instance.

Notes

The provided information suggests a specific instance issue rather than a general problem with n8n. The Cloudflare timeout (HTTP 524) indicates an issue with the origin server's response time, which may be related to the workflow's state or the IMAP connection.

Recommendation

Apply a workaround by manually deleting the stuck workflow from the database/server level and restarting the affected worker process, as this directly addresses the reported issue and clears the conflicting workflow state.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#environment variable#network issue#logging issue#authentication issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING