Here's a structured table for the error messages related to the Viva Engage connector, including a brief description of potential causes for each error:
S.No. | Connector Name | Condition | Error Message | Potential Causes |
1 | Viva Engage | If any required input field is missing | Value does not exist for property: (ABC) | Required fields (like username, password, clientID, etc.) are not provided in the request. |
2 | Viva Engage | If Username is wrong | Response status code does not indicate success: 401 (Unauthorized) | The username provided does not match any existing account in Viva Engage. |
3 | Viva Engage | If password is wrong | Response status code does not indicate success: 401 (Unauthorized) | The password provided is incorrect for the given username. |
4 | Viva Engage | If clientID is wrong | Response status code does not indicate success: 401 (Unauthorized) | The clientID provided does not match the registered application in Azure AD. |
5 | Viva Engage | If groupUrl is not valid | Invalid URL or Group identifier not found in the URL | The URL format is incorrect, or the specified group does not exist or is inaccessible to the application. |