temporalio / temporalio/temporal
Provide already-existing run ID on StartChildWorkflowExecutionFailedEventAttributes if it failed for "already exists"
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Describe the solution you'd like
Need the already-exists run ID on StartChildWorkflowExecutionFailedEventAttributes when the child start fails because it already exists. This already is present on WorkflowExecutionAlreadyStartedFailure for clients. No opinion on what to call the field, can just be existing_run_id so as not to confuse people into thinking it's the actual child's run ID (which would be impossible since it failed to start).
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 with the StartChildWorkflowExecutionFailedEventAttributes and WorkflowExecutionAlreadyStartedFailure definitions and trace how the already-exists failure is converted into the child-start failure event. Confirm where the existing run ID is available, then add it to the event attributes and cover the already-exists path with tests showing the ID is preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100