Monitor job status and statistics

You can monitor the outcome of enrichment jobs using the D&B Job Execution Statistics lookup table and D&B Logs for detailed errors. This applies across batch, real-time, monitoring, and recertification flows.

Each job record shows the processing mode, record count, error summary (if applicable), and duration. You can use this information to diagnose failures or performance issues.

Review email notifications

Job summaries are sent via email to recipients defined in the Email for RIH Job Notifications environment property. Notifications include filters, run mode, status, duration, and failure counts.

To configure multiple recipients, add comma-separated email addresses in the lookup table property.

Troubleshoot issues using logs

Use the D&B Logs lookup table to access detailed error messages when a job fails. Logs are stored in FileStorage and also reflected in the UI.

If failure rates are high, use the Workato Dashboard to inspect recipe execution steps and task failures.

Enable or disable enrichment modes

To control enrichment traffic, start or stop the relevant trigger recipes. This allows you to isolate real-time, batch, or monitoring flows.

Real-Time

Start/stop D&B | TRG-SQS | Real Time Enrichment to enable or pause real-time record processing.

Batch

Use D&B | TRG | Scheduler for Batch Enrichment and D&B | API | REST API for Batch Enrichment to control scheduled and API-triggered batch jobs

Monitoring

Start/stop D&B | TRG | Monitoring Trigger Recipe to control S3-based monitoring events.

Trigger enrichment from external tools

You can send enrichment requests from Postman or external apps using the API Platform token. Be sure to enable the API endpoints in Tools → API Platform.

For batch enrichment, use:

POST https://apim.workato.com/xxxxx/trigger-recipes/batchEnrichment?filter={{filter}}&doNotMerge={{flag}}

For real-time enrichment, use:

POST https://apim.workato.com/xxxxx/trigger-recipes/dev-dnb-api-real-time-enrichment-rest-api?doNotMerge=true&dataBlocks=companyinfo_L3_v1&entityURI={{entityURI}}

Set the api-token and Content-Type: application/json headers.

Understand known observations

Some common operational observations may include:

• If your API keys or secrets are rotated, update them in Connections and Properties immediately.
• If your registration limit is reached, new DUNS won’t be added to monitoring until cleared.
• Monitoring recipes skip records that lack the required URI:DUNS crosswalk.
• Batch jobs may show discrepancies in failure counts if retry logic succeeded after first failure.