Skip to contentSkip to navigationSkip to topbar
Page tools
Useful for sharing or LLM
Accelerate development with AI

On this pageProducts used
Looking for more inspiration?Visit the
Error
Application error

60301: Entity already exists

Twilio Verify DocumentationVerify

Description

description page anchor

This error indicates that your request tried to create a Verify Entity with an Identity that already exists in the same Verify Service. Twilio returns HTTP 409 for this conflict because each Entity Identity must be unique within a Service.

Possible causes

possible-causes page anchor
  • You sent a Create Entity request with an Identity that is already assigned to another Entity in the same Verify Service.
  • Your application retried the same request and attempted to create a duplicate Entity.
  • Your application does not check whether the Entity already exists before creating a new one.
  • You are reusing the same Identity value across multiple users or records in the same Service.
  • Use a unique Identity value for each Entity in the Verify Service.
  • Check whether the Entity already exists before you send a Create Entity request.
  • If you intended to work with an existing Entity, fetch or update that Entity instead of creating a new one.
  • Review your retry and idempotency logic to prevent duplicate create requests.
  • Confirm that your application maps each user to only one Entity per Verify Service.

Additional resources

additional-resources page anchor