Duplicate Enrollment Error in FACEIO Integration

Hi everyone,

We're running into a duplicate enrollment error (code 7) while integrating FACEIO. The system indicates that facial features are already recorded, but we don't have the corresponding facialId stored locally. This is likely due to some initial integration hiccups.

Here's the situation:

* FACEIO enrollment is blocked due to duplicate face detection.
* Our local database doesn't contain the relevant facialId.
* We're unable to delete the existing record because we don't know the original facialId.
* Duplicate prevention is disabled in the console.
* The issue persists after clearing the cache and restarting the application.

Has anyone else encountered this? We're looking for guidance on how to remove or reset the existing enrollment so we can continue testing. Any advice on recovering the associated facialId would also be greatly appreciated.

Thanks in advance for your help!

If you are encountering FACEIO error code 7 (duplicate enrollment) during enroll(), it means the system has already detected that the same face was previously registered in your application.

This can happen even if:

The user has previously enrolled in your application, either intentionally or unintentionally (possibly during your testing phase).
Your local database does not store the facialId
Your integration previously failed or was incomplete

Why this happens

The facial recognition engine used by FACEIO stores templates independently of your local database. So even if your app does not have the facialId, the face may still exist in your application index.

How to Fix It

1. Retrieve the existing facialId

Go to your FACEIO Console → Application Manager → Metrics tab

The Metrics tab logs recent successful enrollments
You will find the associated facialId there
This is the ID you need to manage or delete the record

2. Delete the existing record

Once you have the facialId, call the DELETEFACIALID API endpoint:

https://faceio.net/rest-api#deletefacialid

This will immediately remove the biometric template from the index.

3. Retry enrollment

After deletion:

Call enroll() again
The user should now be able to register successfully

Best Practice

Always store the facialId returned during enrollment in your database. This allows you to:

Manage users properly
Delete or update biometric records
Avoid orphaned enrollments

Summary

If you see duplicate face detected (error 7) and don’t have the facialId:

Retrieve it from the Metrics tab
Delete it using the API
Re-enroll the user

This is a common issue during development and initial integration, especially when testing enrollment flows multiple times.