cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

When integration tasks fail, an error is logged in the integration task log files. Use your log file and the table below to locate the error and determine the resolution.

note blue light.pngNote: If the initial integration immediately fails and no tasks are run, usually there is a permissions issue or an issue with the values entered during authorization. Please verify that the correct steps were followed in the integration instructions, then reauthorize.

 

Locating integration task log files

The integration task log files are in the integration tab. There is a download link for each task which allows you to download the log file for each task that failed. 

1. Go to SaaS > Managed SaaS Applications.

saas- managed saas.png

2. Select the Microsoft application that is failing integration from the Managed SaaS Applications list, then select the Integration tab.

integ.png

3. The integration task log files are located under the Logs column. Select Download next to the failed task to view the log.

download.png

4. Open the log file and scroll to the bottom to find the error that occurred.

In the example log file below, the task failed with error 422 Unprocesseable Entity.

Example

code exmaple.PNG

5. Use the chart below to look up the resolution based on the error code you received.

Integration errors and resolutions

Error Common scenarios Resolution

401 Unauthorized

Refresh token is revoked/expired

 

Authorization failure

 

Entered invalid user credentials

A user with integration permissions must re-authorize the integration.

 

If credentials are invalid, re-enter valid credentials and retry.

 

403 Forbidden
Invalid permission

The application access task fails but the application roster task continues to execute without any issues

The user needs to be assigned report reader permission.

403 Forbidden
User is not in the allowed roles

All integration tasks fail

The user account which authorized integration is deleted. You will need to re-authorize the integration.

 

API permissions have not been added to the app in the Azure portal or authorization by the account admin is pending.

404 Not Found

NA

Contact support team for debugging.

422 Unprocessable Entity

The user who authorized the integration changed their password or it was reset by the account admin

 

Another user with the required permissions should reauthorize the integration.

Was this article helpful? Yes No
No ratings
Version history
Last update:
‎Jul 07, 2022 10:21 AM
Updated by: