Troubleshooting
Learn how to test, debug, and optimize your integration using Workforce Verification in RiskOS™.
Common errors
The table below outlines common errors that may occur during Workforce Verification in RiskOS™. These issues can result from input formatting problems, incomplete data, or workflow misconfiguration. Understanding these patterns can help you debug workflows and apply appropriate routing.
| Issue | Explanation | Suggested fix |
|---|---|---|
| Top of the funnel passive check did not get triggered | The event_type parameter was not set properly, so the workflow did not route to the passive checks at the top of the funnel. | Ensure the event_type field in the request to the RiskOS™ Evaluation API matches the applicant stage (e.g., application_submitted). |
| Document Verification did not get triggered | The request did not include the parameters required to route to Document Verification. | Ensure the event_type field is set to a stage where Document Verification is required. Also include docv.config in the request and set docv.config.send_message = true. |
| Enrichment step returned an error | Required fields for the products in the Workforce Verification workflow were not passed in the request. | Include applicant’s first name, last name, email, phone number, country, and di_session_token (if using Socure Digital Intelligence). Validate that all required fields exist. |
Updated about 1 month ago