Skip to content

Move timeout default from schedule_to_close to start_to_close #969

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.

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

Closed
wants to merge 1 commit into from

Conversation

tconley1428
Copy link
Contributor

What was changed

Why?

Checklist

  1. Closes

  2. How was this tested:

  1. Any docs updates needed?

@tconley1428 tconley1428 requested a review from a team as a code owner July 14, 2025 23:28
"""Maximum time from scheduling to completion."""

schedule_to_start_timeout: Optional[timedelta] = None
"""Maximum time from scheduling to starting."""

start_to_close_timeout: Optional[timedelta] = None
start_to_close_timeout: Optional[timedelta] = timedelta(seconds=60)
Copy link
Member

@cretz cretz Jul 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO we should not do this until we are also properly differentiating retryable vs non-retryable errors on the model activity. If someone has an auth failure, it will now retry forever. Can we except-and-re-raise model activity failures as application error properly accounting for what is retryable and what's not (basically 4xx HTTP is non-retryable, 5xx is retryable, or some variant of that logic)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants