run-llama/chat-ui
1
0
Fork 0
mirror of https://github.com/run-llama/chat-ui.git synced 2026-07-22 03:45:20 -04:00
Code Issues 13 Packages Projects Releases 10 Wiki Activity

useWorkflow status is undefined until it recieves its first event #24

New Issue
Closed
opened 2026-02-16 02:17:44 -05:00 by yindo · 2 comments
yindo commented 2026-02-16 02:17:44 -05:00
Owner
Copy Link
Copy Source

Originally created by @adrianlyjak on GitHub (Jun 25, 2025).

I was testing out the new useWorkflow hook. My workflow is long running, and wasn't actually writing any events to the stream (yet). This seems to cause the workflow handler's status to remain undefined. Sending an initial event fixed the issue, and updated the status, but seems like this should be able to consider the workflow running after sending the initial start event

Originally created by @adrianlyjak on GitHub (Jun 25, 2025). I was testing out the new `useWorkflow` hook. My workflow is long running, and wasn't actually writing any events to the stream (yet). This seems to cause the workflow handler's status to remain `undefined`. Sending an initial event fixed the issue, and updated the status, but seems like this should be able to consider the workflow running after sending the initial start event
yindo closed this issue 2026-02-16 02:17:44 -05:00
yindo commented 2026-02-16 02:17:44 -05:00
Author
Owner
Copy Link
Copy Source

@marcusschiesser commented on GitHub (Jun 27, 2025):

@llamaindex/chat-ui@0.5.11 now sets status to running after the task is started - @adrianlyjak does that work for you?

@marcusschiesser commented on GitHub (Jun 27, 2025): @llamaindex/chat-ui@0.5.11 now sets status to `running` after the task is started - @adrianlyjak does that work for you?
yindo commented 2026-02-16 02:17:44 -05:00
Author
Owner
Copy Link
Copy Source

@adrianlyjak commented on GitHub (Jun 27, 2025):

@marcusschiesser that sounds good! Thanks. The semantics of the change here seem good. I’m a little mystified as to what I was running into initially, as I couldn’t really recreate it. Llamadeploy also seemed to be streaming correctly in a test, and I didn’t look into it further

@adrianlyjak commented on GitHub (Jun 27, 2025): @marcusschiesser that sounds good! Thanks. The semantics of the change here seem good. I’m a little mystified as to what I was running into initially, as I couldn’t really recreate it. Llamadeploy also seemed to be streaming correctly in a test, and I didn’t look into it further
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
pull-request
Mirrored from GitHub Pull Request
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/chat-ui#24
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?