Troubleshooting
This page contains a list of common errors and known issues encountered while integrating Keka HR 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].
KEK-100-A: The API key/Client ID/Client Secret used to connect the integration is invalid
This error occurs when connecting Keka HR to Zluri with invalid authentication credentials.
To resolve this error, make sure to:
- Carefully follow the instructions for obtaining the correct credentials mentioned in the integration document
- Contact your Keka account manager to obtain the correct:
- Client ID
- Client Secret
- API Key
- Copy the credentials as-is while entering them in Zluri and ensure there are no missing characters
- Verify that your Subdomain matches your organization name (if you use
orgname.keka.com
to log in, useorgname
as the subdomain)
Afterwards, try to connect Keka HR to Zluri again.
KEK-100-B: The API key/Client ID/Client Secret used for this integration is expired/revoked
This error occurs when the authentication credentials used to connect Keka HR to Zluri have expired or been revoked.
To resolve this error:
- Contact your Keka account manager to obtain fresh credentials:
- Client ID
- Client Secret
- API Key
- Follow the instructions in the integration document to reconnect using the new credentials
KEK-101-A: The user trying to connect the integration does not have sufficient permissions to read users
This error occurs when the Keka HR user does not have the necessary privileges to access employee data in Keka.
To resolve this error:
- Ensure the user account has permission to read users (employees) in Keka HR
- Contact your Keka administrator to modify the user permissions
- Verify that the user can access the employee directory in Keka HR before attempting to connect
Try to connect the integration again after confirming the permissions.
KEK-101-B: The permissions for the user who connected the integration have been modified/revoked
This error occurs when the Keka HR user who connected to Zluri has lost the required permissions to access employee data.
To resolve this error:
- Contact your Keka administrator to restore the user's permission to read users (employees)
- Verify that the user can access the employee directory in Keka HR
- Reconnect the integration after confirming the permissions have been restored
KEK-102-A: The subdomain used to connect the integration is invalid
This error occurs when connecting Keka HR to Zluri with an incorrect subdomain.
To resolve this error:
- Verify your organization's Keka subdomain
- If you log in to Keka using
orgname.keka.com
, then your subdomain should beorgname
- Ensure there are no typos in the subdomain field
- Do not include
.keka.com
in the subdomain field - only enter the organization name
Try to connect the integration again with the correct subdomain.
KEK-102-B: The subdomain used for this integration is invalid
This error occurs when the subdomain used for the Keka HR integration has become invalid or has been changed.
To resolve this error:
- Verify your current organization's Keka subdomain
- Check if your organization's Keka URL has changed
- If you log in to Keka using
orgname.keka.com
, then your subdomain should beorgname
- Reconnect the integration using the correct subdomain
If you're unsure about the correct subdomain, contact your Keka administrator for confirmation.
If your issue is not listed here, please contact Zluri support with the error details for further assistance.
Updated about 15 hours ago