This repository was archived by the owner on Sep 2, 2025. It is now read-only.
Context import bug fix #66
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue:
NameError: name 'Context' is not definedDescription
The error occurs because the
Contextobject is referenced in thedispatch_callsfunction but was not imported at the beginning of the script.The
Contextclass is essential for managing workflow execution inllama_index, particularly when handling multiple tool calls in a sequential or parallel fashion.** Root Cause**
dispatch_callsis defined as:ctx: Contextis expected as an argument, butContextis not defined or imported anywhere in the script.NameError: name 'Context' is not definedwhen the workflow runs.** Fix: Import
Contextfromllama_index**To resolve the issue, add the missing import at the beginning of the script:
This ensures that the
Contextobject is recognized when used indispatch_callsand other functions that require workflow execution management.** Impact of the Fix**
RouterOutputAgentWorkflow.