Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[WHY] Why you would see activity schedule_to_close timeout or start to close timeout not default values: 0/30 #195

Open
longquanzheng opened this issue Feb 28, 2023 · 0 comments
Open

[WHY] Why you would see activity schedule_to_close timeout or start to close timeout not default values: 0/30 #195

longquanzheng opened this issue Feb 28, 2023 · 0 comments
Labels
documentation Improvements or additions to documentation question Further information is requested

Comments

@longquanzheng
Copy link
Contributor

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.
@longquanzheng longquanzheng added documentation Improvements or additions to documentation question Further information is requested labels Jul 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation Improvements or additions to documentation question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@longquanzheng