Troubleshoot
Fix common BambooHR integration errors
This page lists common errors and known issues encountered while integrating BambooHR 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].
BAM-100-A: The organization that you are trying to connect is not found
This error occurs if the organization’s BambooHR domain entered while connecting BambooHR to Zluri does not exist. To fix this:
- Carefully follow the instructions for finding the BambooHR domain in the Connect the BambooHR instance in Zluri part of the integration document.
- Copy the BambooHR domain as-is while entering it in Zluri and ensure there are no spelling errors or missing characters.
Afterwards, try to connect BambooHR to Zluri again.
BAM-100-B: The organization used for this integration is deactivated/not found
This error occurs if the organization name/subdomain used to connect BambooHR to Zluri has been deactivated.
To fix this, make sure the BambooHR organization account exists and is active. Afterwards, follow the instructions in the integration document and try to reconnect the integration.
BAM-101-A: The API key used to connect the integration is invalid
This error occurs while connecting BambooHR to Zluri with an invalid API key. To fix this:
- Carefully follow the instructions for API token generation mentioned in the integration document.
- Copy the API key as-is while entering it in Zluri and ensure there are no missing characters.
Afterwards, try to connect BambooHR to Zluri again.
BAM-101-B: The API key used for this integration has expired or been revoked
This error occurs if the API key used to connect BambooHR 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.
Updated about 2 months ago