Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix Workflow stuck in active state — cannot deactivate or delete [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#29730•Fetched 2026-05-05 06:03:02
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
lautotttlautottt
Participants
lautotttlautotttn8n-assistant[bot]n8n-assistant[bot]
Timeline (top)
commented ×1labeled ×1mentioned ×1subscribed ×1

Error Message

Describe the problem/error/question

What is the error message (if any)?

GET /api/v1/workflows/ptslc2Xsotq5BXDp via API → error code: 502

  • error: all

Code Example

(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.
RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

Describe the problem/error/question

Workflow is stuck in active state and cannot be deactivated or deleted. I accidentally deleted all nodes from the workflow while trying to deactivate it. The workflow now has no nodes but still shows as active in the UI. All attempts to deactivate it fail.

Workflow ID: ptslc2Xsotq5BXDp Instance: lauto.app.n8n.cloud

What is the error message (if any)?

Deactivating via UI → Workflow could not be deactivated: Request failed with status code 524 POST /api/v1/workflows/ptslc2Xsotq5BXDp/deactivate via API → no response body, workflow remains active GET /api/v1/workflows/ptslc2Xsotq5BXDp via API → error code: 502

Please share your workflow/screenshots/recording

The workflow has no nodes (they were deleted). There is nothing to copy/paste from the canvas.

(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

<!-- If you need help with data transformations, please also share your expected output. -->

N/A — workflow has no nodes and no recent executions.

Debug info

Workflow could not be deactivated: Request failed with status code 524

Request: Please force-deactivate or delete this workflow from the backend so I can reimport it from scratch. Thank you.

core

  • n8nVersion: 2.18.5
  • platform: docker (cloud)
  • nodeJsVersion: 24.14.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/147.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-05-04T18:02:51.739Z

extent analysis

TL;DR

The workflow is likely stuck due to inconsistent state after node deletion, and a force-deactivate or delete operation from the backend is needed to resolve the issue.

Guidance

  • Verify the workflow's current state by checking the API response for GET /api/v1/workflows/ptslc2Xsotq5BXDp to confirm it still returns an active status.
  • Attempt to force-deactivate the workflow using the API with administrative privileges, if available, to bypass the UI limitations.
  • If force-deactivation is not possible, consider reaching out to the n8n support team for assistance with manually deleting the workflow from the backend.
  • Before re-importing the workflow, ensure that the new workflow configuration is correct and complete to avoid similar issues in the future.

Notes

The provided information suggests that the issue is specific to the workflow's state after node deletion, and resolving it may require direct backend intervention.

Recommendation

Apply workaround: Reach out to the n8n support team for assistance with manually deleting the workflow from the backend, as this seems to be the most direct way to resolve the stuck 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#model compatibility#GPU setup#container setup#orchestration 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