temporalio / temporalio/temporal
Carry over signal to retry execution if original was created via SignalWithStart
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
If client creates execution using SignalWithStarts and defines workflow retry policy.
If original execution created fails, the retry does not include the signal thats also sent via SignalWithStart exec creation. It currently only includes the workflow inputs of the initially created exec.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how SignalWithStart creates an execution and how retry state is assembled after the original execution fails. Verify the behavior with a workflow that has a retry policy and receives a signal during SignalWithStart; done means the retry receives that signal as well as the original workflow inputs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100