How to remove/configure resilience in Destination Service

[lixingwang]

Ask the Question

Hi Team,

We’re building an SAP-managed solution that relies heavily on Destinations for cross‑application communication.
For several reasons, we’d like to ignore Destination 404 errors and proceed with an alternative flow. However, we’re currently hitting a circuit breaker OPEN issue:

com.sap.cloud.sdk.cloudplatform.connectivity.exception.DestinationNotFoundException: 
com.sap.cloud.sdk.cloudplatform.resilience.ResilienceRuntimeException: 
CircuitBreaker 'class com.sap.cloud.sdk.cloudplatform.connectivity.DestinationServiceSingleDestResilience' 
is OPEN and does not permit further calls. Triggered by

Since Cloud SDK uses resilience4j, I’m looking for the following options—please let me know if either is supported:

1. Expose resilience configuration so we can treat DestinationNotFoundException as ignored/not counted failures (i.e., do not trigger the circuit breaker).
2. Disable resilience per Destination instance (opt out the circuit breaker for specific Destinations).

If neither is possible, we intend to build a custom client that calls the Destination REST API directly to check for existence before proceeding(We lost the cloud SDK existing caching etc features)

Please advise.

[Jonas-Isr]

Hi @lixingwang,

The Cloud SDK does not offer support for the circuit breaker configurations you are describing. But we recently developed a new feature that (as far as I understand your question) should help you.

The new feature prepends an additional check to tryGetDestination: when a single destination is called, it is first checked whether this destination appears in the result of a get-all-destination call. If the destination is not present, no call to the destination is made. This improves the circuit breaker, as the circuit breaker now does not open unnecessarily when non-existing destination(s) are called multiple times.

Would this feature solve your problem? It will be available in the next Cloud SDK release.