n8n - 💡(How to fix) Fix Workflow he0yM199upHBZ3MX ("Autopy 2026 - Demo Reminders Calendly") desapareció completamente del editor de 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#28267Fetched 2026-04-10 03:44:32
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Timeline (top)
closed ×1commented ×1labeled ×1

Error Message

What is the error message (if any)? error: all

Fix Action

Fix / Workaround

Cronología Se realizó un PATCH exitoso vía API pública para actualizar un parámetro del nodo "If" (caseSensitive: true → false) usando la herramienta n8n_update_partial_workflow Posteriormente se intentaron varios PATCH y PUT adicionales que fallaron con errores de validación (nunca se aplicaron) Después de estos intentos fallidos, el workflow dejó de ser visible en el editor UI, aunque la API lo sigue retornando completo Impacto Workflow de producción con 60 nodos activo e invisible Wait nodes pendientes ejecutándose sin poder monitorearse No hay opción de "Restore" en el historial de versiones del editor El workflow no aparece en ningún proyecto ni en el espacio personal What is the error message (if any)? En el editor al acceder por URL directa:

RAW_BUFFERClick to expand / collapse

Workflow he0yM199upHBZ3MX ("Autopy 2026 - Demo Reminders Calendly") desapareció completamente del editor de n8n Cloud. No aparece en la lista de workflows del proyecto, no se pueden ver ejecuciones, y al acceder por URL directa (/workflow/he0yM199upHBZ3MX) redirige a un workflow nuevo vacío.

Sin embargo, el workflow sigue existiendo y activo a través de la API REST pública (GET /api/v1/workflows/he0yM199upHBZ3MX devuelve los 60 nodos y 56 conexiones completas). Las ejecuciones también se pueden consultar por API. Incluso al intentar transferir el workflow a otro proyecto, la API responde: "You can't transfer a workflow into the same destination it already belongs to", confirmando que el workflow está en el proyecto correcto.

El workflow tiene Wait nodes activos con ejecuciones pendientes que se siguen ejecutando en el backend pero no son visibles ni gestionables desde el editor.

Cronología Se realizó un PATCH exitoso vía API pública para actualizar un parámetro del nodo "If" (caseSensitive: true → false) usando la herramienta n8n_update_partial_workflow Posteriormente se intentaron varios PATCH y PUT adicionales que fallaron con errores de validación (nunca se aplicaron) Después de estos intentos fallidos, el workflow dejó de ser visible en el editor UI, aunque la API lo sigue retornando completo Impacto Workflow de producción con 60 nodos activo e invisible Wait nodes pendientes ejecutándose sin poder monitorearse No hay opción de "Restore" en el historial de versiones del editor El workflow no aparece en ningún proyecto ni en el espacio personal What is the error message (if any)? En el editor al acceder por URL directa:

Workflow not found We couldn't find the workflow you were looking for. Make sure you have the correct URL. Please share your workflow/screenshots/recording Workflow ID: he0yM199upHBZ3MX Proyecto: OF6ZE1MjllK0PCF9

Respuesta de la API confirmando que el workflow existe:

{ "id": "he0yM199upHBZ3MX", "name": "Autopy 2026 - Demo Reminders Calendly", "active": true, "isArchived": false, "nodeCount": 60, "connectionCount": 56, "updatedAt": "2026-04-09T15:56:19.212Z" } Respuesta al intentar transferirlo al mismo proyecto:

{"message":"You can't transfer a workflow into the same destination it already belongs to."} Share the output returned by the last node N/A - el problema es de visibilidad en el editor, no de ejecución.

Debug info core n8nVersion: 2.15.0 platform: docker (cloud) nodeJsVersion: 24.13.1 nodeEnv: production database: sqlite executionMode: regular concurrency: 50 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 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/146.0.0.0 safari/537.36 isTouchDevice: false

extent analysis

TL;DR

The workflow "Autopy 2026 - Demo Reminders Calendly" is not visible in the n8n Cloud editor, but it still exists and is active through the API, suggesting a potential issue with the editor's workflow listing or caching.

Guidance

  • Verify that the workflow ID is correct and try accessing it through the API again to confirm its existence.
  • Check the n8n Cloud editor's workflow listing settings to ensure that the workflow is not filtered out or hidden.
  • Attempt to create a new workflow and then try to transfer the invisible workflow to the new one to see if it becomes visible.
  • Review the API responses for any clues about the workflow's status or potential errors.

Example

No code snippet is provided as the issue seems to be related to the n8n Cloud editor's workflow listing or caching, rather than a code-specific problem.

Notes

The issue may be specific to the n8n Cloud editor or the workflow's configuration, and further investigation is needed to determine the root cause. The fact that the workflow is still active and accessible through the API suggests that the issue is not related to the workflow's functionality, but rather its visibility in the editor.

Recommendation

Apply a workaround by trying to transfer the workflow to a new project or creating a new workflow and then trying to access the invisible one. This may help to identify the issue or make the workflow visible again.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING