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

# 60441: Illegal status

Log Type: TWILIO

Log Level: ERROR

## Description

This error indicates that Verify encountered a verification status it could not process for the current operation. Verify statuses can be `pending`, `approved`, `canceled`, `max_attempts_reached`, `deleted`, `failed`, or `expired`. If you update a verification directly, the update endpoint only supports `approved` and `canceled`. For most verification flows, use the Verification Check API to validate the code and let Verify manage the lifecycle.

### Possible causes

* A verification operation returned an unexpected status.
* Your application attempted to update a verification with a status other than `approved` or `canceled`.
* Your integration is using manual verification status updates for a flow that should be completed with the Verification Check API.

### Possible solutions

* If you call Update a Verification Status, send only `approved` after your application has validated the code or `canceled` when you need to start a new verification session.
* Use the Verification Check API for normal OTP validation so Verify can manage the verification lifecycle.
* Review the verification in Verify Logs in Console to confirm the status that was returned. If you continue to receive 60441 for valid requests, contact Support with the Verify Service SID and Verification SID.

#### Additional resources

* [Verify API: Verifications](/docs/verify/api/verification)
* [Verify API: Verification Check](/docs/verify/api/verification-check)
* [Verify overview](/docs/verify)