Audit log offers a record of important events in your Greenhouse Recruiting environment from the previous 30 days. If you're receiving errors or unexpected results with audit log, a few troubleshooting steps can help get you back on track.
Audit log API errors
Some audit log API errors can be resolved by double-checking your request. Here are a few tips:
- Use bearer token authorization, with a valid access token.
- Use the correct HTTP method. Most audit log requests are made with GET.
- Use valid query parameters.
JWT is missing or invalid
A JWT error means that your access token has expired, is missing, or isn't valid for your organization. Access tokens are only valid for 24 hours. Here are a few tips:
- Verify that you're using bearer token authorization with a valid access token.
- If needed, generate a new access token from Harvest API.
- For development, create a process to programmatically generate new access tokens once daily.
Error status codes
Here are some common API status code responses and how to resolve them:
|401||Unauthorized — Your access token is invalid or has expired. Access tokens expire in 24 hours. Ensure you're using a valid access token in the authorization header.|
|403||Forbidden — You don't have access to that record.|
|404||Not found — The resource wasn't found.|
|422||Not processed — We're not able to process your request. Validate your parameters.|
|429||Rate limit exceeded — You're being throttled for exceeding our rate limit.|
|500||Server error — We're having a problem with our server. Give us a few minutes and try again, or check our status page.|
Audit log errors on Business Intelligence Connector
Some errors with audit log on Business Intelligence Connector can be resolved by double-checking your query. Here are a few tips:
- Check your query. Ensure you're using proper syntax and querying the expected tables. Check out the Entity Relationship Diagram (ERD) for information on how tables and columns relate to each other.
- Check your connection. If you're receiving login rejected or auth failed, there's an issue with your Business Intelligence Connector settings. Learn more.
Connection timed out
Connection timed out is a general error that can happen during a query. Here are a few tips:
- Try running a smaller query to see if the action still times out. Sometimes very large queries can cause timeout issues.
- Check if your organization's network is limiting traffic, which can cause queries to time out. Your IT team will be able to verify this issue.
- Verify that Redshift is still connected to your organization. Learn more.
Audit log retains up to 30 days of data starting from the time that it's enabled for an organization. If you've just recently enabled audit log, you may not be seeing data in Business Intelligence Connector for this reason.
Business Intelligence Connector shares your organization's data in nightly ETLs, so you should expect refreshed data once daily. If you're missing data in the table, wait for your organization's next ETL to complete.