Turn off schedule_to_start activity timeout by default #119
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
As shown in the comments, the temporal team strongly recommends against using
schedule_to_starttimeout unless you're doing things like manually re-routing to different task queues.We have also run into struggles with this timeout. I think the best policy is to remove the default.
Test Plan
bundle exec rspec ./spec/unit/lib/temporal/configuration_spec.rb