Enrichment Error Handling

RiskOS™ integrates with multiple enrichment modules and data partners. To ensure reliability, the platform includes built-in mechanisms to handle errors gracefully and allow workflows to continue executing even when individual steps encounter issues.

Retry mechanism

RiskOS™ automatically retries failed enrichment API calls up to three times, with a maximum wait time of 2,000 ms per attempt.

If you need to adjust retry behavior for your account, please contact support@socure.com.

Handling enrichment failures in workflows

This ensures workflows continue executing instead of failing completely.

Identifying errors in API responses

All enrichment results are returned in the evaluation API response under the data_enrichments array.

Each enrichment block includes:

Tip: An enrichment call is considered successful if status_code = 200. Any non-200 response means the enrichment failed.

Example request

Failed enrichment request

{
  "enrichment_name": "Socure Email Risk",
  "enrichment_endpoint": "https://sandbox.dev.socure.com/api/3.0/EmailAuthScore",
  "enrichment_provider": "Socure",
  "status_code": 500,
  "error_message": "Internal Server Error. Unable to process email risk request at this time.",
  "request": {
    "modules": [
      "emailrisk"
    ],
    "email": "johnsmith123+test@example.com"
  },
  "is_source_cache": false,
  "total_attempts": 3
}