Skip to content

[Fix]: generator node connectored to batch node - #9453

Open
dunkeroni wants to merge 1 commit into
invoke-ai:mainfrom
dunkeroni:fix_generator_connectored_to_batch
Open

[Fix]: generator node connectored to batch node#9453
dunkeroni wants to merge 1 commit into
invoke-ai:mainfrom
dunkeroni:fix_generator_connectored_to_batch

Conversation

@dunkeroni

Copy link
Copy Markdown
Collaborator

Summary

Utilizes the existing connector resolver when calculating batch values. Previously having a connector between generator and batch node would cause the calculation to hang, preventing the user from running the workflow.

Related Issues / Discussions

Closes #9150

QA Instructions

Add one or more connectors between the generator and batch node. See that the Invoke button still works. Tooltip should show the number of generations, not "Loading..."
image

Merge Plan

Ready to merge

Checklist

  • The PR has a short but descriptive title, suitable for a changelog
  • Tests added / updated (if applicable)
  • ❗Changes to a redux slice have a corresponding migration
  • Documentation added / updated (if applicable)
  • Updated What's New copy (if doing a release after this PR)

@github-actions github-actions Bot added the frontend PRs that change frontend files label Aug 3, 2026
@JPPhoto

JPPhoto commented Aug 3, 2026

Copy link
Copy Markdown
Collaborator

@dunkeroni I haven't tried this workflow or PR, but does it allow for 1-to-N fan-out of the generator output at any connector? Was this allowed without connectors?

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

Labels

frontend PRs that change frontend files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[bug]: Having a connector between a generator and a batch node won't let Invoke start a generation

2 participants