fightBoxing opened a new issue, #1407: URL: https://github.com/apache/flink-agents/issues/1407
### Search before asking - [x] I searched in the [issues](https://github.com/apache/flink-agents/issues) and found nothing similar. ### Description The built-in chat retry treats every provider failure as retryable. A 400 spends the whole `max-retries` budget and the backoff, even though the same request will fail again. Retry classification should be: - Do not retry HTTP 4xx other than 408, 409, and 429. - Do retry 408, 409, 429, 5xx, timeouts, and failures that carry no HTTP status. - Read the status from the exception or its cause, so a wrapper does not hide a client error. - Keep a recorded client error non-retryable on recovery. An older durable outcome that has no such flag stays retryable. Addressed by #1405. ### Are you willing to submit a PR? - [x] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
