---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/91300#article
headline: "91300: Event delivery to sink failed"
url: https://www.twilio.com/docs/api/errors/91300
inLanguage: en
dateModified: 2026-10-27T17:14:57.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 91300: Event delivery to sink failed

Log Type: APPLICATION

Log Level: ERROR

## Description

Twilio records this generic delivery failure error when Event Streams cannot deliver an event to your configured sink and the failure does not match a more specific error condition.

This error serves as a generic fallback and is recorded when Twilio cannot identify the precise root cause such as a timeout, connection error, or specific HTTP status.

### Possible causes

* A non-webhook sink (such as AWS Kinesis, Segment, etc) rejected the write payload due to invalid stream names, missing permissions, or invalid credentials.
* The sink rejected or dropped the delivery payload under conditions that fall outside standard HTTP or protocol-specific error categorizations.

### Possible solutions

* Review your sink error logs for more granular errors that provide specific remediation steps.
* Verify that the sink actually exists, is active, and is not in a deleting or paused state.
* Ensure that the API keys, IAM roles, write permissions, or authorization tokens configured on the sink are active and have write access to the sink.

### Related errors

* [91305: Sink endpoint rejected the event](/docs/api/errors/91305)
* [91306: Sink endpoint returned a server error](/docs/api/errors/91306)
* [91307: Could not connect to sink endpoint](/docs/api/errors/91307)
* [91308: Sink endpoint did not respond in time](/docs/api/errors/91308)

#### Additional resources

* [Event Streams overview](/docs/events)
* [Sink resource](/docs/events/event-streams/sink-resource)
* [Subscription resource](/docs/events/event-streams/subscription)