Troubleshoot

This page lists common errors and known issues encountered while integrating Personio 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].

PER-100-A: The Client ID and Client secret used are invalid

This error occurs when the client ID and/or client secret entered during integration is incorrect. To fix this:

• Carefully follow the instructions for retrieving the client ID and secret in the integration document.
• Copy the client ID and secret as-is while entering it in Zluri and ensure there are no missing characters.

Afterwards, try to connect Personio to Zluri again.

PER-100-B: The Client ID and Client secret used earlier have expired or been removed. Use a new Client ID and Client secret to reconnect the integration

This error occurs if the API key used to connect Personio to Zluri has expired or been revoked.

To fix this, create a new API token by following the instructions in the integration document and try to reconnect the integration.

PER-101-A: We are not getting all the attributes required for an employee. Please ensure that you whitelist the required attributes

This error occurs if all the Readable employee attributes weren’t selected while creating the Personio API token.

To fix this, check all the boxes in the Readable employee attributes section during API token generation, then try to connect Personio to Zluri again.

PER-101-B: We are unable to get all the required attributes for an employee. Please ensure that you whitelist the required attributes

This error occurs if the Personio API token used to connect the integration has lost all or some of the Readable employee attributes permissions.

To fix this, check all the boxes in the Readable employee attributes section during API token generation, then reconnect the integration.