Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split the processing of workflow-based and chat-based runs #1694

Open
thedadams opened this issue Feb 10, 2025 · 1 comment
Open

Split the processing of workflow-based and chat-based runs #1694

thedadams opened this issue Feb 10, 2025 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@thedadams
Copy link
Contributor

If too many workflow-based runs are running, then this can lead to chat-based runs not getting processed. We should have a way to split the processing of runs so that this backup does not occur.

@thedadams
Copy link
Contributor Author

To test this:

  1. Run Obot with NAH_THREADINESS=1.
  2. Save the following tool (or an equivalent version) to your local machine:
Name: sleep
Description: Sleep for some number of seconds
Args: seconds: The number of seconds to sleep

#!/usr/bin/env sh
sleep ${SECONDS}
  1. Add this tool in the UI.
  2. Create a workflow.
  3. Add a step to this workflow, adding the above tool and giving it the following instructions: Sleep for 120 seconds
  4. Run this workflow from the UI. Optionally, in another browser tab, run the workflow again. You should see that the second workflow's run doesn't start until the first one finishes.
  5. In another browser window, chat with any agent. This should succeed without waiting for the workflows to finish.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant