hatchet icon indicating copy to clipboard operation
hatchet copied to clipboard

bug(engine): Steps Remain in Running State After Worker Restart with Unawaited registerWorkflow

Open grutt opened this issue 1 year ago • 0 comments

Steps to reproduce:

  1. Start a worker without awaiting for the response from registerWorkflow async function main() { const worker = await hatchet.worker('example-worker'); worker.registerWorkflow(workflow); worker.start(); } NOTE: the worker does not have any actions assigned

  2. trigger an event to the workflow. this will immediately spawn

  3. fix the worker (add the async) and restart

  4. trigger a new event.

Both the initial event and all subsequent events are stuck in a running state.

Expected behavior: The initial step should fail with no workers available. Future steps should be picked up by the worker.

grutt avatar Feb 29 '24 01:02 grutt