temporalio / temporalio/temporal
Limit depth of child workflows
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
Currently there is no ability to limit number of levels of child workflow creation. It can potentially lead to situations when due to programming mistake workflow keeps creating children recursively forever.
Describe the solution you'd like
Allow configurable depth limit for child workflow creation.
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 locating the child workflow creation path in the Go service and tracing how parent and child workflows are represented. Determine where a configurable depth limit belongs and how exceeding it should be reported. Done means recursive child creation is prevented at the configured limit and the behavior is covered by relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100