temporalio / temporalio/temporal
trigger one workflow from another workflow
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
I was wondering if it was possible to trigger one workflow using another workflow? For instance: can workflow A trigger workflow B and can workflow B access outputs from workflow A's activity?
We want to build two different workflows for two different teams that share the same temporal server
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
The issue asks whether one workflow can trigger another and share activity outputs, but it names no files, tests, or entry points. Start by clarifying the intended workflow relationship and output-sharing semantics in the Temporal server; a complete issue should identify the affected subsystem, expected behavior, and acceptance tests.
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