---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/17564#article
headline: "17564: Webhook payload exceeds maximum size"
url: https://www.twilio.com/docs/api/errors/17564
inLanguage: en
dateModified: 2026-10-02T00:01:43.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 17564: Webhook payload exceeds maximum size

Log Type: APPLICATION

Log Level: WARNING

## Description

Twilio completed the transcription, but skipped the status callback because the serialized webhook payload exceeded the 1 MB limit.

The transcription record itself is unaffected and still reports as `completed`. Unless you have set a `conversationConfigurationId`, only the status callback delivers the transcript content. If you haven't, you can't recover the content, because fetching a transcription returns its metadata and not the transcript.

### Possible causes

* The transcription ran long and contains many sentences.
* The word-level details in the result exceed 1 MB when serialized.

### Possible solutions

* Set a `conversationConfigurationId` on your Transcription Configuration. This results in Twilio storing the transcript. When the callback isn't delivered, you can retrieve it. You can create a configuration with the [Conversations API](/docs/api/conversations/v2/configuration/create-configuration), in the Twilio Console, or through [Conversation Orchestrator](/docs/conversations/orchestrator).
* Set this in advance for critical workloads. It can't be applied retroactively to a transcription whose callback has already been skipped.

### Additional resources

* [Receive transcription results with a webhook](/docs/voice/api/batch-transcription-resource#receive-transcription-results-with-a-webhook)
* [Transcribe a Twilio Recording](/docs/voice/api/batch-transcription-resource#transcribe-a-twilio-recording)