Enrich From Note Troubleshooting

If the Enrich from Note automation step isn't working as expected, this troubleshooting guide can help. We've compiled solutions to the most common issues so you can get back on track quickly.

For a guide to troubleshooting the Enrich from Prompt and Enrich from File steps, see Amplify Enrich Troubleshooting.

Record shows as “Waiting” at the “Async Step Execution” Stage

When a record shows “Waiting” instead of “Complete” at the Async Step Execution stage, it means Bullhorn Automation is waiting for the ATS to finish processing the enrichment request and return a result.

Records are processed one at a time, and each record can take upwards of one minute to complete. If a large number of records are moving through the Enrich from Note step, overall processing time will be longer.

This is expected behavior. Records will automatically change to “Complete” once the ATS has finished processing them. No manual action is required.

The Enrich From Note step has overwritten previous content in a field

This is expected behavior. If your selected field already contains data, the AI-generated content will replace it completely.

Best practices to avoid losing data:

The Enrich from Note step can only change fields that are configured under Enrich Fields on the Entity Settings tab in Amplify Admin. To avoid overwriting existing data, make sure this list only includes fields you are comfortable replacing.

I can’t see the information populated by the Enrich From File step

If the enriched data isn’t visible on the candidate record, check the following:

Once these fields are unhidden and added to the View Layout, the enriched data will appear as expected.

The Enrich from Note step did not update a record as expected

Check the following:

  • The fields you expect to update are included in your Enrich Fields configuration under Admin > Amplify Admin > Entity Settings.

  • The note matches one of the selected action types and the candidate is listed in the About field, not Additional References.

  • The extracted value met or exceeded the configured confidence threshold.

    • To test this, edit the note in the ATS and review the confidence level shown for the relevant field update.

The expected note type was not used for enrichment.

If the step is configured to look for multiple note action types, it will only process the single most recent note that matches any of the selected types. If you want to capture the most recent note of each type separately, consider splitting enrichment into multiple steps, one per note action type. See Select Note Action for more detail.