---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/91301#article
headline: "91301: Destination is disabled"
url: https://www.twilio.com/docs/api/errors/91301
inLanguage: en
dateModified: 2026-11-04T19:15:20.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 91301: Destination is disabled

Log Type: APPLICATION

Log Level: WARNING

## Description

Twilio records this error when Data Destinations attempts to deliver an event to a destination with a `disabled` status.

Because the destination is disabled, Twilio immediately drops the event. Events dropped are lost permanently and cannot be queued, retried, or re-delivered.

### Possible causes

* The destination status was manually set to `disabled` via the API.
* Twilio automatically set the destination to `disabled` after a period of sustained delivery failures.

### Possible solutions

* Ensure your target destination is online, reachable, and correctly configured to receive events.
* If the destination was disabled automatically, check your error logs to identify and resolve the root cause. For more details, see [Error 91300: Event delivery to destination failed](/docs/api/errors/91300).
* Once your destination is healthy, update the destination status back to `active` via the API to resume event delivery.

#### Additional resources

* [Data Destinations overview](/docs/data-destinations)
* [Create a destination](/docs/data-destinations/api-quickstart#create-a-destination)
* [Create a subscription](/docs/data-destinations/api-quickstart#create-a-subscription)
