Skip to main content
This page is for the admin or help desk lead with a stuck verification in front of them. When you finish, you have the likely cause and the fix, or the request ID and event IDs support will ask for. Most problems trace back to a small set of causes: directory data quality, link delivery, camera access on desktops, or use case rule order.

Directory connection

See Microsoft Entra ID for the full setup.
Where exclusive sessions are enabled for your workspace, each link is held by the first browser that opens it. This blocks link forwarding, but it also fires when a user opens the link on a laptop and then switches to a phone. Have the user close the page on the first device, wait about a minute, and reload the link. If the first device is unavailable, send a new link. The QR handoff on the verification page moves to a phone without triggering this, so prefer it over opening the link twice.

Camera: desktop webcams and phone handoff

This is the most common source of failed Face and Proofing steps. Desktop webcams frequently fail capture: the page loops on “move closer” and “move further”, or the camera never starts because the browser window is narrow enough to render the mobile layout. Phone QR handoff succeeds where the webcam does not.
Recommend the phone by default. Brief agents to tell callers “scan the QR code with your phone” rather than “use your laptop camera”. The handoff keeps the same request and link.

Factor failures

Phone number formatting and coverage. SMS delivery requires E.164 (+15551234567); values like 555-123-4567 are rejected. SMS coverage is often far lower than email coverage, and many organizations restrict SMS. Check coverage of the mobile attribute in Settings → Directory before relying on the SMS factor, normalize numbers in the directory, and prefer Email in the primary column.
Email codes are occasionally delayed; the resend works. If delivery problems are widespread, confirm your email security gateway allows the sending domain and check quarantine. Contact support to confirm sender authentication for your workspace.
Resends are limited and a cooldown is shown on the button. This is expected, not a delivery fault. Have the user wait out the countdown; if they exhaust the resend budget, the flow falls back to the next column or the agent sends a fresh link.
The Face factor needs a reference photo. Users with none are routed to a fallback column. Two data-quality problems are common: directory photos are often stale (years old) or tiny (thumbnailPhoto at roughly 96 pixels), and both lower match scores. A photo deposited from a passed Proofing check matches far better. Configure the Face factor’s reference sources so proofing-derived photos take precedence, and put Proofing in a fallback column so users without a usable photo create one. Check photo coverage under Settings → Directory.
The attribute behind the question is empty or inconsistent. department in particular is often blank or formatted differently across business units, and many organizations keep the real org data in extension attributes. Check coverage and sample values in attribute mapping before enabling an attribute as a question source, map the extension attribute that actually holds the data, and disable attributes with poor coverage. See Attribute mapping and coverage.
Read the factor outcome reason on the request timeline. Common causes are capture quality, an unsupported or damaged document, a name that does not match the directory record, or a liveness failure. Have the user retry on a phone in better light. If failures persist for a legitimate user, follow your escalation procedure rather than creating repeated new links.

ServiceNow connector

See ServiceNow.

Storage

Wrong flow for someone

Still stuck?

Activity in the IDV Console is the fastest diagnostic tool: filter to the affected request or user and read the reason codes. See Audit events. When you contact support, include the request ID and the relevant event IDs.