temporalio / temporalio/temporal
Support SignalExternalWorkflowExecutionWithStart
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
There is a Workflow Command for Signaling an External Workflow Execution, but that typically means that the author of the WF has to write code that ensures the workflow is already running and/or start the workflow separately.
SignalExternalExecutionWithStart would make this experience a lot easier
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 the existing SignalExternalWorkflowExecution command and the workflow-start path to understand how they currently coordinate. The issue does not name files or tests; done would mean supporting a combined signal-and-start operation that removes the need for callers to ensure the external workflow is already running or start it separately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100