[Workflow] Workflow hangs when running an activity that can't fulfill DI requirements
- Dominant language
- C#
- Stars
- 1.2k
- Forks
- 378
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 6
Description
## Expected Behavior
When a workflow activity is created that has DI dependencies that haven't not yet been registered with the DI system the workflow should throw an exception that it wasn't able to create the activity.
## Actual Behavior
The workflow quietly hangs giving no indication why the activity isn't executing.
## Steps to Reproduce the Problem
1. Create Activity that requires a dependency injected into it.
2. Don't register the service to be injected
3. Run the workflow
4. Observe that the workflow hangs with no indication of any issue with the activity.
## Release Note
RELEASE NOTE:
Contributor guide
Research direction
Reproduce the workflow with an activity that has an unregistered dependency, then trace activity creation and dependency-injection failure handling. Done means the workflow reports an exception explaining that the activity could not be created instead of hanging silently.
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