I was asked to implement both @CircuitBreaker and @Retry patterns in a project where a CustomExceptionHandler (@ControllerAdvice) is used to perform interceptions.
As custom outputs (based on custom models) are being returned instead of default exceptions, none of them are being executed.
Both @CircuitBreaker and @Retry patterns have some parameters to trigger themselves when specific exceptions occur, but the application is not having exceptions, but custom response entities.
Is there any idea to fix this conflict? Resilience4j's documentation doesn't include anything similar.