# Bamboo HR - Error checking for new jobs

The 403 Forbidden error indicates that you do not have permission to access the data necessary to perform an action. For example, you have permission to access employee records, but not their salaries. If your recipe involves performing an action with the employee salaries, but Workato cannot access their salaries with your account permissions, the recipe will fail.

bamboo-hr-403-trigger-error Example of 403 forbidden error message in the recipe trigger

# Solution

If the 403 forbidden error occurs in the recipe trigger, there are no network tracing available for debugging. Instead, build a recipe to quickly identify the specific record that is causing the error. Follow these steps to create a recipe to iterate through all the records and log any errors that it encounters:

  1. Setup the recipe with the scheduler trigger.
  2. Insert the BambooHR: List employees in directory action.
  3. Configure the Repeat action.
  4. Insert the Employees list datapill in the Input list field.
  5. Select the One item at a time mode.
  6. Insert a Handle errors action.
  7. Below the Handle errors: Monitor action, insert a Get employee details by ID action. In the Employee ID field, insert the Step 2: ID datapill.
  8. Below the Handle errors: On error action, insert a Logger by Workato action. In the message field, insert the Step 2: ID datapill to help you identify the records with errors.
  9. Run the recipe and review the output of the Logger by Workato action to see which records require that you have additional permissions to access.

# Why does this error occur?

This can occur when the credentials used to connect Workato to your application do not have the necessary permissions to access the data. For example, sensitive data like Social security numbers require deeper permissions. This may prevent Workato from accessing those records in particular.

Normally, you can use network tracing to troubleshoot and identify the particular record that is causing the issue. However, if this occurs in the recipe trigger, there is no network trace to use for troubleshooting.

For polling triggers, Workato will attempt to re-poll a failed job. This prevents the recipe from running.


Last updated: 3/17/2021, 10:04:31 AM