How to debug an error

After viewing integration errors, you can debug them so that the integration runs smoothly for your users.

You can identify the type of error by looking at the error code which are universal 3-digit numerical codes. When you see an error code for a particular step or run in your logs, it means that the app successfully made contact with a service's servers, but may or may not have actually completed the request due to one of the following situations:

400-Bad request 

The request was unacceptable. This happens mostly when a required parameter is missing.

401-Unauthorized

The request was not authorized because no valid API credentials were provided.

402- Request Failed

The request failed even though the parameters provided were valid. There can be multiple reasons this happens.

403- Forbidden

The access was forbidden because the API credentials provided don't have permission to perform the request.

404 - Not Found

The resource that was requested doesn't exist.

409 - Conflict

There is a conflict of your request with some other request. This can be due to a number of reasons including use of the same key or parameter already existing the in app which you want to create.

429 - Too Many Requests

The API has received too many requests in a short time. 

500-series error codes

Error codes in the 500 series are server errors, which happen when an app’s server is down or experiencing other issues.

Other error codes

You may see a status code that’s not included in the list above. These are non-standard status codes and are likely specific to the app you’re connecting to Integry. If you encounter one of these errors, reach out to the app’s support team for assistance.

Error codes between 400 and 499 are user errors, which happen when the error occurs on Integry’s end.

For more information on HTTP status codes, read MDN Web Docs: HTTP response status codes or HTTP Status Codes for Beginners.

In this example, we will debug the integration error we talked about earlier in the viewing errors article.

We will debug the 400 error in the integration ID 168379 by user: zahranaseem(unj3guuhh)-4342.

When you get to the failed step , you can hover over the network code to see the error definition.

Click on View Payload.

You can diagnose the error in the Response section of the payload.

The Body contains the details on why the 400 error was received.

You can see that one of the member being added to the account already exists.