Skip to content

Broken "Open workflow in new tab" #9101

Open

Description

@intosica

Prerequisites

  • I am running the latest version of ComfyUI
  • I have custom nodes enabled

What happened?

When attempting to do debugging myself, I was pointed to browser console for error code.
This is the one that is produce when trying to active this native ComfyUI feature.
@deprecated Use settingStore.get instead.*/ getSettingValue<K extends keyof Settings>( id: K, defaultValue?: Settings[K]): Settings[K] { if (defaultValue !== undefined) { console.warn(Parameter defaultValue is deprecated. The default value in settings definition will be used instead.)} return useSettingStore().get(id)

I asked for help in Discord, I've tried to fix myself. Also determined in Discord that this is a universal issue, and has been going on for maybe over a couple of weeks now.
Everything points likely to some hardcoded error with a script regarding API usage.

Please fix.
and I guess in the meantime, what has everyone else been using to pull there open workflow in new tab?
Because my downloads folder is filling up, and my production time as been bad having to wait for the first preview to generate just to work on that workflow again.

Steps to Reproduce

1.Run a generation
2.Click on three dots icon for the generation running
3.Click "Open workflow in new tab"

How is this affecting you?

Feature doesn't work as expected

ComfyUI Frontend Version

1.39.14

Browser

Other

Console Errors

`@deprecated Use settingStore.get instead.*/
getSettingValue<K extends keyof Settings>(
  id: K,
  defaultValue?: Settings[K]): Settings[K] {
  if (defaultValue !== undefined) {
    console.warn(Parameter defaultValue is deprecated. The default value in settings definition will be used instead.)}
  return useSettingStore().get(id)`

Logs

Additional Context

No response

┆Issue is synchronized with this Notion page by Unito

Activity

  1. added theissue type on Feb 22, 2026
  2. added
    area:uiGeneral user interface and experience improvements
    on Feb 22, 2026
  3. dosubot commented on Feb 22, 2026

    @dosubot

    Hi @intosica! I'm Dosu and I’m helping the ComfyUI_frontend team.

    This is a known issue that's already being tracked in Issue #8841. It affects versions 1.38.13 through 1.40.1.

    What's happening: The feature fails silently because the workflow metadata extraction looks for a deeply nested structure (workflow.extra_data.extra_pnginfo.workflow). If any part of that path is missing, it fails without showing any user-facing error—only a console warning like [extractWorkflow] Workflow validation failed:.

    Note: The deprecation warning you're seeing (@deprecated Use settingStore.get instead) is not causing the issue—it's a separate cosmetic warning from an older component.

    Workaround: Check your browser console for [extractWorkflow] Workflow validation failed: messages to confirm this is the issue. Unfortunately, there's no direct fix available yet on the user side.

    To reply, just mention @dosu.


    Share context across your team and agents. Try Dosu.

    Leave Feedback Learn about ComfyUI_frontend with Dosu Add Dosu to your team

  4. github-actions commented on Mar 26, 2026

    @github-actions
    Contributor

    QA 🐛 Issue Reproduce

    QA Badge

    Linux QA

    Run: https://github.com/Comfy-Org/ComfyUI_frontend/actions/runs/24466581866 · Download artifacts · All videos
    Commits: main 52ccd9e

    Video Review

    linux QA Video Report

    • Generated at: 2026-04-15T17:03:05.551Z
    • Model: gemini-3-flash-preview
    • Target: Broken "Open workflow in new tab" #9101
    • Source video: ./qa-artifacts/qa-report-Linux-24466581866/qa-session.mp4
    • Video size: 2.7 MB

    AI Review

    Phase 1: Blind Observation

    • 00:00 - 00:03: The user is at the ComfyUI login screen. They click on the "Existing user" dropdown and select the user "qa-ci". They then click the "Next" button.
    • 00:04: The main ComfyUI interface loads with an empty canvas.
    • 00:05: The "Templates" modal window opens automatically (or is triggered by an unseen click). The "Getting Started" section is visible.
    • 00:06 - 00:07: The user hovers over the "1.1 Starter - Text to Image" template card and clicks the "Node graph" link at the bottom of the card.
    • 00:08: The template nodes (Checkpoint Loader, CLIP Text Encode, KSampler, etc.) populate the graph area.
    • 00:09 - 00:15: The interface remains static. No further mouse clicks, keyboard interactions, or menu navigations are observed. The "Run" button is visible at the top but is not clicked. The generation queue/history is not opened.

    Audio: No narration detected.

    Phase 2: Compare against expected behavior

    Issue #9101 Evaluation

    The reported issue requires three specific steps to reproduce:

    1. Run a generation: This step was NOT SHOWN. Although a workflow was loaded from a template, the "Run" button was never clicked.
    2. Click on three dots icon for the generation running: This step was NOT SHOWN. No generation was active, and no history/queue menus were interacted with.
    3. Click "Open workflow in new tab": This step was NOT SHOWN.

    The video terminates before any of the reproduction steps are attempted. The session only shows the prerequisite of loading a workflow but fails to initiate a generation or attempt to use the feature in question.

    Summary

    The video is INCONCLUSIVE. The reproduction steps described in Issue #9101 were not performed. The user successfully loaded a workflow from the template library but stopped the session before running a generation or attempting to access the "Open workflow in new tab" feature.

    Confirmed Issues

    No issues confirmed from the video as the reproduction was not attempted.

    Possible Issues (Needs Human Verification)

    • Session incomplete: The recording ends abruptly after loading a template, failing to follow the test case instructions.

    Overall Risk

    LOW - No UI regressions were observed in the basic login and template loading flow, but the core functionality under test was not reached.

    Narration

    No narration detected.

    Verdict

    {"verdict": "INCONCLUSIVE", "risk": "low", "confidence": "high", "narrationDetected": false}

  5. added 3 commits that reference this issue on Mar 27, 2026
    7d3ddbf
    2e1785e
    8994f74
  6. hum-ma commented on Jun 18, 2026

    @hum-ma

    Issue #8841 has been closed with a supposed fix targeted for 1.45 but the bug is still present in frontend version 1.45.15

    in the meantime, what has everyone else been using to pull there open workflow in new tab?

    I don't think there's any way to recover them other than trying to remember all the settings yourself.

  7. lnsflive commented on Nov 4, 2026

    @lnsflive

    Additional findings from frontend 1.57.4, including a useful comparison with Assets:

    The user reports that Assets can open the same completed API-submitted jobs as workflows, while the Queue action does nothing. Assets also works for some jobs whose output image file is missing.

    Code and job-record inspection explains the API-submitted case: those jobs retain workflow.prompt but omit extra_data.extra_pnginfo.workflow. Assets falls back to loading the stored API graph through app.loadApiJson; Queue only calls getJobWorkflow and silently returns when editor workflow data is absent. The relevant installed frontend sources match the official v1.57.4 tag exactly.

    There are also two relevant findings for unfinished jobs:

    • In the inspected backend, comfy_execution/jobs.py:get_job returns normalize_queue_item for pending/running jobs. That response omits the workflow field expected by the frontend opening action.
    • jobOutputCache.ts:getJobDetail caches these responses by job ID, with no completion invalidation or refresh in that cache module. An unfinished snapshot can therefore remain in use after the job completes, until cache eviction or page reload.

    Related PR #10929 proposes the API-graph fallback. PR #22890 proposes a warning instead of silently returning.

    Scope: this does not explain every reported failure. Some completed browser-submitted jobs contain editor workflows that passed the frontend workflow schema validation; their opening failure remains unconfirmed. This investigation used read-only code/job inspection, not an invocation of the opening action, and did not change the running queue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Potential BugUntriaged bugarea:uiGeneral user interface and experience improvements

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions