You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Does calling register_workflow after worker.start() support ?
#3851
Hello I am working on a dynamic workflow scenario where the worker will watch filesystem change in one folder and dynamically registering/deleting workflows. But right now I am seeing that if I call register_workflow after worker.start(). The workflow is registered with the engine but isn't registered with the worker itself (the "Registered Workflows" section in the worker does not have the newly created workflow and trigger the workflow results in an error because no worker can run it). Registering workflow before starting worker works well.
Is it a bug or is it expected behavior ? Thank you very much!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hello I am working on a dynamic workflow scenario where the worker will watch filesystem change in one folder and dynamically registering/deleting workflows. But right now I am seeing that if I call
register_workflowafterworker.start(). The workflow is registered with the engine but isn't registered with the worker itself (the "Registered Workflows" section in the worker does not have the newly created workflow and trigger the workflow results in an error because no worker can run it). Registering workflow before starting worker works well.Is it a bug or is it expected behavior ? Thank you very much!
All reactions