## Troubleshooting

### 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.

## FAQs

### Why is identity verification important throughout an employee's lifecycle?
Comprehensive [identity verification](/content/glossary/identity-verification/index.html) safeguards sensitive company data and supports regulatory compliance from onboarding through offboarding. Ongoing checks at key stages help mitigate risks tied to [identity theft](/content/glossary/identity-fraud-management/index.html), unauthorized access, and [data breaches](/content/glossary/data-breach/index.html), reinforcing stakeholder trust and reducing legal and financial exposure.

### What challenges do employers face when verifying remote workforce identities?
Remote verification is harder without in-person interaction, increasing reliance on digital documents and authenticity checks. Organizations must also navigate varying jurisdictional requirements, which complicates [compliance](/content/glossary/compliance/index.html) and elevate fraud-prevention needs (see [fraud prevention](/content/glossary/fraud-prevention/index.html) and [identity proofing](/content/glossary/identity-proofing/index.html)).

### Can Socure help detect risky employees in my organization?
Yes. RiskOS™ can flag high-risk employees via configurable signals, including:
- PII verification
- Email / phone / address risk
- Digital Intelligence
- Synthetic fraud detection

RiskOS™ also supports retroactive Predictive DocV. Socure assigns a persistent identity token (SocureID) to support ongoing risk checks and re-verification throughout the employee lifecycle.

### How should I think about Workforce Verification relative to background checks?
Workforce Verification delivers real-time identity and document verification to catch stolen, synthetic, and manipulated identities before background checks begin. Workforce Verification confirms identity up front; background checks validate criminal history and credentials. Together they create a stronger, end-to-end defense against inbound workforce fraud.

### Does Socure support hosted flows and end-user experience?
Yes. Socure enables branded Workforce Verification flows that deliver a seamless, customizable UX. With RiskOS™, you can quickly launch verification experiences with minimal lift and integrate at any stage of the employment lifecycle.

### How does SocureID help with Workforce Verification?
Powered by AI, billions of monthly events, and a large performance-outcome graph, Socure's identity network learns continuously in real time. SocureID's persistent identity links applicants across hiring stages, making it easier to recognize trusted identities and focus on anomalies—so every interaction makes the network smarter.

Updated about 2 months ago