run-llama/workflows-py
1
0
Fork 0
mirror of https://github.com/run-llama/workflows-py.git synced 2026-07-21 04:05:25 -04:00
Code Issues 18 Packages Projects Releases 10 Wiki Activity

[Bug] Debugger UI does not provide required boolean StartEvent properties when they are set to false. #30

New Issue
Closed
opened 2026-02-16 02:16:11 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 02:16:11 -05:00
Owner
Copy Link
Copy Source

Originally created by @SamHill-InnoSys on GitHub (Jan 2, 2026).

If a subclassed StartEvent requires a boolean parameter, and you set it to False when starting the workflow through the debugger, the parameter does not get passed to the event. This causes a Pydantic validation error:

{ detail:"Validation error for 'start_event': Failed to deserialize event: 1 validation error for CustomStart\nfoo\n Field required [type=missing, input_value={'message': 'a'}, input_type=dict]\n For further information visit https://errors.pydantic.dev/2.12/v/missing" }

Versions

llama-index-core                  0.14.10
llama-index-workflows             2.11.5
pydantic                          2.12.5
pydantic-core                     2.41.5

Steps to Reproduce

  1. Create a subclass of StartEvent:
class CustomStart(StartEvent):
    message: str
    foo: bool
  1. Create and register a workflow that consumes this StartEvent
  2. Run llamactl serve and go to localhost:4501/debugger
  3. Select the workflow and try to run it with foo=false
  4. Note that nothing happens. View browser console and see the request fail with the validation error.

Extra

Can be avoided by supplying a default value:

class CustomStart(StartEvent):
    message: str
    foo: bool = False

but that might not be optimal.

Originally created by @SamHill-InnoSys on GitHub (Jan 2, 2026). If a subclassed StartEvent requires a boolean parameter, and you set it to False when starting the workflow through the debugger, the parameter does not get passed to the event. This causes a Pydantic validation error: ``` { detail:"Validation error for 'start_event': Failed to deserialize event: 1 validation error for CustomStart\nfoo\n Field required [type=missing, input_value={'message': 'a'}, input_type=dict]\n For further information visit https://errors.pydantic.dev/2.12/v/missing" } ``` ## Versions ``` llama-index-core 0.14.10 llama-index-workflows 2.11.5 pydantic 2.12.5 pydantic-core 2.41.5 ``` ## Steps to Reproduce 1. Create a subclass of StartEvent: ``` class CustomStart(StartEvent): message: str foo: bool ``` 2. Create and register a workflow that consumes this StartEvent 3. Run `llamactl serve` and go to `localhost:4501/debugger` 4. Select the workflow and try to run it with `foo=false` 5. Note that nothing happens. View browser console and see the request fail with the validation error. ## Extra Can be avoided by supplying a default value: ``` class CustomStart(StartEvent): message: str foo: bool = False ``` but that might not be optimal.
yindo closed this issue 2026-02-16 02:16:11 -05:00
yindo commented 2026-02-16 02:16:12 -05:00
Author
Owner
Copy Link
Copy Source

@adrianlyjak commented on GitHub (Jan 6, 2026):

Fix released in v2.11.7

@adrianlyjak commented on GitHub (Jan 6, 2026): Fix released in v2.11.7
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
enhancement
good first issue
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/workflows-py#30
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?