Troubleshooting Digital Assistant Issues

Assistant isn't loading

Check if the ODA server URI and Bot channel ID are correct. See Creating Bot Definitions.

Assistant isn't responding to a message

Make sure the channel is routed to the appropriate skill or digital assistant.
Turn off client authentication.
In Allowed Domains, enter * to allow requests from all domains.

You could also restrict the value to a PeopleSoft domain.

See Creating a Channel.

Error messages

Error	Solution
Oops! I'm encountering a spot of trouble. Please try again later.	ODA may be down. Wait until ODA is up and running.
Oops! Something went wrong while connecting to PeopleSoft. Check your network connection, or contact your system administrator.	Try the following solutions: In ODA, check the yaml code of the skill for syntax errors, and correct these errors if they exist. Navigate to PeopleTools, and then Utilities, and then Administration, and then Message Catalog. Check if any of the message catalog numbers specified in the yaml code of the skill exist in PeopleSoft. Navigate to PeopleTools, and then Security, and then User Profiles, and then User Profiles. Make sure that the user PSFTPROXY exists, isn't locked out, and has the appropriate roles. If it's locked out, unlock the account and reset the password. If you reset the password, you need to run through Updating the Custom Component Package of a Skill again to update PSFTPROXY's password. Ensure the environment's JSON file has the correct URL, user ID, and password for PSFTPROXY. See Updating the Custom Component Package of a Skill. In ODA, ensure that the parameters of the skill in the digital assistant are correct. See Connecting to a PeopleSoft Application Service.
Failed to sign in! Please check your credentials and try again.	This error appears either because the skill doesn't have the EOCB_CLIENT_USER or an incorrect role is assigned to it. To assign the role: From Campus Solutions, navigate to PeopleTools, and then Integration Broker, and then Application Services, and then Administration, and then Application Services Security. In Bulk Permissions, look for the appropriate App Service ID, Index, Method, and Root Resource of the skill, then click the corresponding Set Security. Make sure EOCB_CLIENT_USER is assigned, and that it has full access. If it isn't assigned, then add it. Save your changes.

Error

Solution

Oops! I'm encountering a spot of trouble. Please try again later.

ODA may be down. Wait until ODA is up and running.

Oops! Something went wrong while connecting to PeopleSoft. Check your network connection, or contact your system administrator.

Try the following solutions:

In ODA, check the yaml code of the skill for syntax errors, and correct these errors if they exist.
Navigate to PeopleTools, and then Utilities, and then Administration, and then Message Catalog. Check if any of the message catalog numbers specified in the yaml code of the skill exist in PeopleSoft.
Navigate to PeopleTools, and then Security, and then User Profiles, and then User Profiles. Make sure that the user PSFTPROXY exists, isn't locked out, and has the appropriate roles. If it's locked out, unlock the account and reset the password.

If you reset the password, you need to run through Updating the Custom Component Package of a Skill again to update PSFTPROXY's password.
Ensure the environment's JSON file has the correct URL, user ID, and password for PSFTPROXY. See Updating the Custom Component Package of a Skill.
In ODA, ensure that the parameters of the skill in the digital assistant are correct. See Connecting to a PeopleSoft Application Service.

Failed to sign in! Please check your credentials and try again.

This error appears either because the skill doesn't have the EOCB_CLIENT_USER or an incorrect role is assigned to it.

To assign the role:

From Campus Solutions, navigate to PeopleTools, and then Integration Broker, and then Application Services, and then Administration, and then Application Services Security.
In Bulk Permissions, look for the appropriate App Service ID, Index, Method, and Root Resource of the skill, then click the corresponding Set Security.
Make sure EOCB_CLIENT_USER is assigned, and that it has full access. If it isn't assigned, then add it.
Save your changes.