Closed cimuletz closed 2 hours ago
Hey @cimuletz, I'm here to help you with any bugs, questions, or contributions you have! Let's tackle this issue together.
The issue you're experiencing with the CancelledError
after 300 seconds, despite setting LANGFLOW_WORKER_TIMEOUT
to 3000, might be due to the precedence of configuration settings. The LANGFLOW_WORKER_TIMEOUT
environment variable is set to 300 by default, and if you're using a CLI command with the --worker-timeout
option, it will override the environment variable. Make sure that the --worker-timeout
option is not set to 300 in your CLI command, or adjust it to 3000 if it is. Also, verify that your .env
file correctly sets LANGFLOW_WORKER_TIMEOUT
to 3000 [1][2].
To continue talking to Dosu, mention @dosu.
Bug Description
I have an LLM evaluation flow which receives CancelledError when component runs longer than 300 seconds.
LANGFLOW_WORKER_TIMEOUT
is set to 3000 so this doesn't seem to be the problem.Reproduction
Following error will occur: asyncio.exceptions.CancelledError
Expected behavior
Components to keep running for however long they take and resume flow with the next component.
Who can help?
@ogabrielluiz @nicoloboschi @zzzming
Operating System
Ubuntu Linux
Langflow Version
1.0.19
Python Version
None
Screenshot
No response
Flow File
No response