Skip to content
This repository was archived by the owner on Jul 5, 2026. It is now read-only.

Fix parallel node functions triggering multiple LLM completions - #244

Open
omChauhanDev wants to merge 2 commits into
pipecat-ai:mainfrom
omChauhanDev:fix/parallel-node-function-multiple-completions
Open

Fix parallel node functions triggering multiple LLM completions#244
omChauhanDev wants to merge 2 commits into
pipecat-ai:mainfrom
omChauhanDev:fix/parallel-node-function-multiple-completions

Conversation

@omChauhanDev

@omChauhanDev omChauhanDev commented Mar 21, 2026

Copy link
Copy Markdown

Fixes : #243, pipecat-ai/pipecat#3925

When the LLM makes multiple parallel calls to the same node function (common with global_functions), each result was triggering a separate LLM completion — producing multiple responses instead of one.

Root cause: node functions explicitly set run_llm=True on each result, overriding pipecat's built-in logic that already knows to wait until all parallel calls finish.

Fix: run_llm=Truerun_llm=None - let pipecat's default handle it.

  • Single calls: no behavior change
  • Parallel calls: LLM now waits for all results before responding

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Parallel node function calls trigger multiple LLM completions

1 participant