[WHY] Why you would see activity schedule_to_close timeout or start to close timeout not default values: 0/30
Open
Nobody has claimed this yet.
documentation
question
- Dominant language
- Go
- Stars
- 661
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Description
This is because Cadence/Temporal will cap the value to the workflow timeout. If the workflow timeout is 10s, then the two timeout will be caped to 10s.
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 body explains the timeout behavior but names no documentation file, entry point, or test. First identify where workflow timeout behavior is documented, then add the explanation there and verify that the documented defaults and capping behavior are accurate.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100