"No Reply" error in SAP CAI Chat console

[roy_pappachan2]

Hi experts,

I'm frequently facing below error ("No Reply" in red colour chat) .There is an API call involved. But my API call is just a simple CDS direct query involved 3 fields from a single row. Whenever it works, the response is quick.

How can I troubleshoot this issue? What is the response time set in SAP CAI to display below message?

When I'm using MS Team Channel, I am not even getting any response for the below case.?

How can I differentiate/troubleshoot the issue whether its a CAI issue or S/4 backend API access issue?

Thanks,

Roy

[roy_pappachan2]

no-reply-error.png

[JonasB]

Hi Roy,

please click on the "i" icon of the last message displayed in "Chat Preview". In the JSON displayed check for the "logs" node and either paste this completely here or compare the entries with what is displayed in the "Debug" list. Based on the order you can find the entries that are causing the "No Code".

The "No Code" is shown when there is a log entry in "logs" which is not properly maintained in the frontend. One known issue where this is currently the case is when there is no intent or entity classification model available for the current language.

Regards
Jonas

[roy_pappachan2]

Hi jonas.brand,

Thanks for the quick response. But when there is such error ( screen shot of error "no-reply-error.png" attached above). We will not have Json log available ( JSON view will be empty) and even debug view with trigger events also stopped with the last intent.

So far I have faced this issues in below cases.

1. Backend system S/4 is too slow.

2. Outage in SAP CAI

3. Some script error in the custom messages. ( Not 100% sure ).

I faced this issue at 7.30PM IST and left the bot as it is . Now( 8.45pm IST) I am checking and its working fine without any "No Reply" error.

I have a proper system connection error and API failure error handling mechanism in my bot. But I am getting "No Reply". So some better error handling mechanism can be done in SAP CAI backend which will tell us exactly what went wrong?

Thanks,

Roy

[JonasB]

Hi Roy,

I see. If that's the case you can open the Network tab in Chrome browser and check for the API call to /api/csr/build/v1/dialog which probably failed. In the response headers you can find the X-CorrelationId which will help us to check what went wrong in the processing, as of course under normal circumstances such error should not occur. Also the HTTP Response code might give you an indication what is wrong, e.g. 503 in case of outages.

Regards
Jonas

[JonasB]

In cases where the API requests to external systems failed, you'll get the status_code as part of the api_service_response variable and can react to it accordingly. Also in cases of the backend being too slow to respond (15 seconds), the skill execution does continue and you can check in your skill if api_service_response variable is empty and react accordingly.

Scripting errors will also not cause the overall execution to fail but only the relevant action will be skipped with an entry in the debug logs indicating this.

Of course there might be exceptional cases were the platform might not treat an error correctly, so in these cases it will help for you to share the correlation ID as described for us to analyze this.

Regards
Jonas

[roy_pappachan2]

Sorry for the delay in response.

Many Thanks Jonas. It will help me for sure.

Next time, when I encounter the same problem. I will troubleshoot in this way.

Its my bad that I didn't think about the browser debug option.

And of course yes, I have handled all possible caused of API call failures with status codes from API response.

<299,

> 299 & <500,

>499.

Thanks,

Roy