Artifact Signing organization validation – Face Check fails at the end with tokenError "The targeted resource in CosmosDB already exists"

Hello,

I am trying to complete an Artifact Signing Public / Organization identity validation for my company (KALKI DRIM MAGAZIN S.R.L., Romania). The individual identity verification keeps failing at the very last step with a server error, not because of my documents or my face.

What happened:

1. 9 Oct 2026, evening: I completed the AU10TIX verification (ID document + selfie) in Microsoft Authenticator. A Verified ID card was issued and is in my Authenticator wallet. That first request was later deleted by me.
2. 10 Oct 2026, ~10:50 (EEST): new request 9b16c3e1-ec7b-43be-a02d-80c95adce528. The browser page showed "Verification successful!", but the phone showed errors, and 11 minutes later the request went to Failed (e-mail "Validation Fail", no reason given).
3. 10 Oct 2026, ~16:45 (EEST): new request 3ab36db0-dc7a-4cba-bdaa-694c6b205ce7, requester name entered exactly as on the Verified ID card. The Face Check passed (green), then at the end Authenticator showed:

   Oh no, something went wrong. We can't continue due to a technical problem with the request. Please try again later.

   Error details:
   • Error code: tokenError
   • Error details: The server cannot fulfil the request due to a server conflict.. The targeted resource in CosmosDB already exists.. The targeted resource in CosmosDB already exists.
   • Request ID: 699e37be-337d-44c7-9b16-0bed3cda9c4
   • Correlation ID: UV9VsWh+RpmHJc9+zfRD7A.5.7
   • Timestamp: 10 Oct 2026, 16:45 EEST (13:45 UTC)

It looks like a duplicate-record conflict on the service side (perhaps from the earlier, deleted request), not a problem with the face match.

Questions:

1. Can you clear the conflicting record so request 3ab36db0-dc7a-4cba-bdaa-694c6b205ce7 can be completed (or re-send a new verification link for it)?
2. Should I remove the existing Verified ID card from Microsoft Authenticator and re-verify before creating another request, or will that cause the same conflict?

I can provide the Subscription ID privately. Thank you.