elsa-workflows / elsa-workflows/elsa-core
IDLE workflows not being picked up again after engine restart.
- Dominant language
- C#
- Stars
- 7.9k
- Forks
- 1.5k
- Avg merge
- 15h 22m
- Merged PRs (30d)
- 114
Description
When I post multiple signals to start a workflow using "dispatch", the workflow instances are created and run one after another which is good. My workflow "RegisterAccount" simply waits 5 seconds, so I could test this issue. See the screenshot below to see what it looks like in the ELSA dashboard.

The problem I face is when I restart the workflow engine. The workflow instance that was RUNNING is continued, but the IDLE instances do not automatically start when the RUNNING instance is finished. This means that the IDLE instances are not being picked up again after the workflow engine is restarted.
Contributor guide
Research direction
No source files or tests are named. Reproduce the issue by dispatching multiple instances of the RegisterAccount workflow, restarting the engine while one is running, and observing the remaining IDLE instances in the Elsa dashboard. Trace how queued instances are resumed after restart; done means the IDLE instances start after the active instance finishes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100