Destination not found exception error from SAP Cloud SDK

[Rositza]

Describe the Bug

Hi colleagues,
can you help this customer who is facing an issue with their Production subaccount.

They are getting the below error in the Cloud SDK

Caused by: com.sap.cloud.sdk.cloudplatform.connectivity.exception.DestinationAccessException: com.sap.cloud.sdk.cloudplatform.connectivity.exception.DestinationNotFoundException: No destination for name '*****' could be found in any of the registered loaders.
Destination service find-api returned successfully the destination, also the destination is visible in Cockpit.

Info from customer "Yesterday I tested the destination using Postman and the response was 200. However, at the same time the application on BTP returned the error "destination not found". This is not the first time we have encountered these kinds of errors with the subaccount, but usually restarting the application solved the issue. Since yesterday, even restarting has not resolved the problem.

Could you please check if there is any issue at the subaccount level? As mentioned, the same code and the same destination work without errors in the TEST subaccount. "

Regards,
Rositza

Steps to Reproduce

1. We are experiencing an issue with the Destination service in our production subaccount Since: 2025-10-01, 12:00 UTC (14:00 CEST)
   From BTP Cockpit → "Check Connection" works fine (destination reachable).
   From Java applications running on Cloud Foundry → all calls to destinations fail with 503 Service Unavailable.
   Error trace:
   Caused by: com.sap.cloud.sdk.cloudplatform.connectivity.exception.DestinationAccessException: com.sap.cloud.sdk.cloudplatform.connectivity.exception.DestinationNotFoundException: No destination for name 'dedoka-api' could be found in any of the registered loaders .
   The issue affects many destinations configured both at subaccount and space level.
2. We have tested the same code and the same destinations in our QUALITY subaccount, and everything works correctly there.
   The issue is reproducible only in the PRODUCTION subaccount (MON_BTP_PRD), while in QUALITY the destination calls return the expected result without errors.
3. Yesterday I tested the destination using Postman and the response was 200. However, at the same time the application on BTP returned the error "destination not found". This is not the first time we have encountered these kinds of errors with the subaccount, but usually restarting the application solved the issue. Since yesterday, even restarting has not resolved the problem.

Expected Behavior

Working scenario and find the destination

Screenshots

No response

Used Versions

Not available have to be provided from customer.

• Java and Maven version via mvn --version: ...
• SAP Cloud SDK version: ...
• Spring Boot or CAP version: ...

Dependency tree via mvn dependency:tree

Dependency tree here

Code Examples

// Your code here

Stack Trace

No response

Log File

Log file

...

Affected Development Phase

Production

Impact

Blocked

Timeline

No response

[rpanackal]

Dear @Rositza,

Thank you for creating the issue.

As a first step, we kindly ask the customer to update to the latest version of the Cloud SDK for Java, since 3.x reached EOL in March 2023. This will help us more effectively identify and diagnose the issue.

Secondly, we would need more detailed logs to proceed further. Could you please help us by providing the HTTP wire logs?

Best regards,
Roshin

[newtork]

Unfortunately, as long as no feedback or further information comes back, we need to close the ticket.
Please feel free to create a new issue with updated data for troubleshooting.

Sensitive information can be shared within the company communication channels (Teams, Slack, Mail) as long as a public issue is created in advance and has an active conversation.