---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/60391#article
headline: "60391: Challenge not found"
url: https://www.twilio.com/docs/api/errors/60391
inLanguage: en
dateModified: 2026-06-08T12:04:59.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 60391: Challenge not found

Log Type: APPLICATION

Log Level: ERROR

## Description

Twilio returns this error when the requested Challenge resource cannot be found in Verify. A Challenge represents a single verification attempt for an Entity using a Factor, and Challenge fetch and update requests are scoped by `ServiceSid`, `Identity`, and the Challenge `Sid`.

### Possible causes

* The Challenge `Sid` in your request does not match an existing Challenge resource.
* The `Identity` value in the request does not match the Entity that owns the Challenge. Verify requires `identity` to be an immutable external identifier, and Challenge operations are scoped to that Entity.
* The `ServiceSid` points to a different Verify Service than the one where the Challenge was created. Challenge requests are nested under a specific Service and Entity path.
* Your application may be reusing a stale Challenge SID or combining values from different Services, Entities, or environments.

### Possible solutions

* Confirm that `ServiceSid`, `Identity`, and the Challenge `Sid` exactly match the values returned when you created or previously fetched the Challenge.
* If you do not have the current Challenge SID, list the Challenges for the Entity and verify that the resource exists before you fetch or update it. You can also filter the list by `factorSid` or `status`.
* Store and reuse the same immutable `identity` value for the user across Entity, Factor, and Challenge operations. Do not substitute a different user identifier in later requests.
* If you need a new verification attempt, create a new Challenge for the correct Entity and Factor, then use the new Challenge `Sid` in subsequent requests.

#### Additional resources

* [Challenge Resource](/docs/verify/api/challenge)
* [Entity Resource](/docs/verify/api/entity)
* [Factor Resource](/docs/verify/api/factor)