maxpfab

Have you fixed it already? I am facing that Issue for more than a year. I found out that with those versions it is working: "@sap-cloud-sdk/connectivity": "3.15.0", "@sap-cloud-sdk/http-client": "3.15.0", "@sap/cds":...

Hi @ChristophMatthies, I wanted to ask if you have already some updates. Best regards, Max

Hello @KavithaSiva, I used now the following packages: "dependencies": { "@cap-js/hana": "^1.9.1", "@sap-cloud-sdk/connectivity": "4.0.3-20250718125934.0", "@sap-cloud-sdk/http-client": "4.0.3-20250718125934.0", "@sap/cds": "^8.9.4", "@sap/cds-mtxs": "^2.7.6", "@sap/xssec": "^4.9.0", "axios": "^1.10.0", "cfenv": "^1.2.4", "express": "^4.21.2", "moment-timezone": "^0.6.0"...

Hi, I have now exported the Logs: [kdperformance-srv-tddoemdevmtx-2025-07-29 07_36_20.575+0000.txt](https://github.com/user-attachments/files/21483279/kdperformance-srv-tddoemdevmtx-2025-07-29.07_36_20.575%2B0000.txt) Hopefully you can find something. Thanks, Max

No worries. I know that problem all too well. I have done that, could I somehow send you those logs? Because there are many credentails inside. And yes that is...

Thats what I also found out, that when you subscribe the service you are able to get the destinations with the xsuaa creds of the provider. Yeah because it is...

So we have a Service Broker which hosts the api from the CAP Service. With the Subscription, the broker gets registred inside of the subscriber subaccount. Now a Broker Instance...

I guess you were right that it was working now. I have missed to add the destinations dependency to the subscription. Did it outside of the cap/requires inside of the...

Perfect :) I have done some more tests and it is now working also with the newest version. "@sap-cloud-sdk/connectivity": "^4.1.1", "@sap-cloud-sdk/http-client": "^4.1.1", Thanks for your efforts. Now I can upgrade...

Hi @ZhongpinWang, Yes in step one, CAP APP 1 is calling the CAP APP 2 with a Destination which has a Broker Instance bound as authorization from CAP APP 2....