anupamraj176 commented on issue #37176: URL: https://github.com/apache/beam/issues/37176#issuecomment-3694038126
Thanks for reporting this — I can confirm this behavior. Wrapping retryable exceptions (such as `UserCodeTimeoutException` and `UserCodeRemoteSystemException`) inside `UserCodeExecutionException` prevents the retry/backoff logic from identifying them correctly, causing these failures to be treated as non-retryable. The suggested fix to rethrow known retryable exceptions (or unwrap them before wrapping) looks correct and aligns with the intended retry classification behavior. It may also be helpful to add unit tests that verify: - retry/backoff is triggered for `UserCodeTimeoutException` - retry/backoff is triggered for `UserCodeRemoteSystemException` - non-retryable exceptions are still wrapped as `UserCodeExecutionException` Happy to help with tests or a PR if needed. -- 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]
