cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Warning: An error occured when calling URL /errors

0 Likes
353

Dear colleague,

since a few days I face the following error:

when I try to write with my chatbot I always get and error and the fallback message, no matter what I write:

Error: Multiple skills have been triggered at the same time: create-delivery,greetings. Try to execute the fallback skill.
Warning: An error occured when calling URL /errors"The URL /errors is a relative path and no base URL is configured in the Settings."

Could you tell me, why I get this error? The displayed multiple skills seem to be wrong to me, as I have checked all intents and entities.

Thank you in advance for your help!

Christina

Accepted Solutions (0)

Answers (1)

Answers (1)

thomas-bruckner
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi Christina,

Actually your error message consists of two different things that need to be considered.

Error: Multiple skills have been triggered at the same time: create-delivery,greetings. Try to execute the fallback skill

When entering your chat message, your bot is not able to identify one single skill that should be executed. I seems you have configured overlapping trigger condition in your greetings and create-delivery skill. Skills should be built in a way, that their triggers do not overlap.

Warning: An error occured when calling URL /errors"The URL /errors is a relative path and no base URL is configured in the Settings."

When an error is occurring during a chat conversation with your users, the SAP Conversational AI platform is currently offering to report error to you / your backend. Background here is, that when your bot is live for production, you want to know when there are issues with your bot and your endusers. Therefore the platform tries to send an error report to /errors of the base URL you have configured in the version of your bot. In your case you have not specified a base URL, therefore the bot is not capable of reporting the issue. This is what the second error says, which is in general not a problem if you don't want to monitor issues of your productive bot.

I hope this helps,

Thomas