Review the information provided to diagnose integration errors.
You can view errors in the integration error log.
Error messages
Response |
Reason |
The record is skipped due to connector settings. The record was not processed because there was another record in the same portion with the same identifier. |
The record was skipped because a record with the same ID had already been processed. |
Failed to process the mapping value |
The new mapping field you created on the integration mapping page exceeds the 256-character limit. |
Field "Role" is not filled in. This is a mandatory field. | The Role, along with the Email and Username fields, must be mapped when you create a user integration. |
[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate... The further processing is impossible. |
Integrations do not support self-signed certificates. To ensure the security of data exchanges between Oomnitza and external servers, integrations can only establish connections with servers that possess trusted certificates issued by recognized Certificate Authorities (CAs). We recommend that you either switch to a CA-issued certificate (recommended) or add the server's self-signed certificate to the trust store (least recommended). |
Sync key value is not populated |
"The primary identifier value is not populated." The field that was selected as the sync key for the integration does not contain a value. When you create an integration, you must select a field as a primary sync key such as a serial number or an email address. To avoid getting this error, you can select one or more fields as secondary sync keys. And, if the primary sync key does not contain a value, such as a serial number, the secondary sync key can be used to identify the records that need to be updated. |
Error codes
Response Code | Reason |
400 | Bad request or issue with the message body. As a first step, try reconfiguring or creating a new credential in Configuration> Security> Credentials. If you continue to receive the error, contact Support. |
401 |
Unauthorized. The credentials are either invalid or have expired. |
403 | Insufficient privileges. You do not have sufficient privileges to access the partner’s API. Ensure that you have the correct access rights or administrator privileges to use the API. Consult the partner's API documentation. |
404, 405 | Not Found, Method Not Allowed. The API URL used in the integration is invalid or is not supported. It is not possible for the user to modify or update the API URL of an integration. Contact Support and include the details of your error message. |
429 |
Too many requests. Too many requests were sent in a session. Check your integration schedule. |
500, 503, 503 | Internal Server Error, Bad Gateway, Service Unavailable. These error messages indicate a problem with the system. Contact support and include the details of the error message. |
If you continue to receive errors after you troubleshoot the errors, contact Support.
Comments
0 comments
Please sign in to leave a comment.