Troubleshoot

Fix common Cornerstone integration errors

This page lists common errors and known issues encountered while integrating Cornerstone with Zluri, and instructions on how to fix them.

If your issue isn’t mentioned here, feel free to submit a ticket or contact us directly at [email protected].

This error occurs when the Cornerstone service user does not have the required privileges to access the Employee API.

To fix this:

Follow the Create a Cornerstone service user account and custom security role section in the integration document.
Make sure the service user role includes the employee:read permission.

Afterwards, try to connect Cornerstone to Zluri again.

This error appears when the service user’s permissions have changed after the initial connection.

To fix this:

Revisit the Create a Cornerstone service user account and custom security role section in the integration document.
Restore the employee:read permission.

Afterwards, reconnect Cornerstone to Zluri.

This error occurs when the Client ID or Secret entered into Zluri does not match the values obtained from Cornerstone.

To fix this:

Follow the Obtain a Cornerstone Client ID and Secret steps.
Copy the Client ID and Client Secret exactly as shown, ensuring no missing or extra characters.

Afterwards, try to connect Cornerstone to Zluri again.

This error appears when the Client ID or Secret has expired or been revoked in Cornerstone.

To fix this:

Follow the Obtain a Cornerstone Client ID and Secret steps.
Copy the new Client ID and Client Secret exactly as shown, ensuring no missing or extra characters.

Afterwards, reconnect Cornerstone to Zluri.

This error occurs when the subdomain entered does not match your Cornerstone instance URL.

To fix this:

Afterwards, reconnect Cornerstone to Zluri.

Updated 12 days ago