Skip to contentSkip to navigationSkip to topbar
Page toolsOn this pageProducts used
Looking for more inspiration?Visit the

60392: Entity not found


ERROR: 60392

error-60392 page anchor
VERIFY
ERROR

This error occurs when your Verify request references an Entity that does not exist in the specified Verify Service. An Entity represents the user identity for Verify Push and Verify TOTP, and Entities are scoped to a single Service.

Possible causes

possible-causes page anchor
  • The identity value in the request does not match an existing Entity in the Service.
  • The request uses the wrong ServiceSid. Entities are not shared across Services.
  • The Entity was deleted before you fetched it or before you created a related Challenge or fetched a related Factor.
  • Your application stored or sent a different identity than the immutable identifier originally used to create the Entity.
  • Send the exact same identity and ServiceSid that you used when you created the user's Entity or Factor.
  • Store the identity consistently across your application. Use an immutable identifier that is 8 to 64 characters long and contains only dash-separated alphanumeric characters.
  • If this is the user's first Verify Push or Verify TOTP enrollment, create a Factor for that identity. Verify creates the Entity automatically when you create a Factor.
  • Fetch or list Entities for the Service before you create or update related Factors and Challenges so you can confirm that the Entity exists.
  • If the Entity was removed, recreate it by creating a new Factor for the correct identity.

Additional resources

additional-resources page anchor