Repository navigation
fix(twilio): answer Twilio's status callbacks with 204 instead of an empty 200 - #1501
Merged
Merged
Conversation
…empty 200
The call status, recording status and transcription callbacks answered with Ok(): a 200 with no body and no content
type. Twilio reads that as a failed callback ("Error reading response: Response does not contain content type") and logs
warning 15003, "Got HTTP 502 response to .../twilio/voice/status", on every call, though the endpoint ran fine. It wants
204 with no body, or TwiML. Nothing else changes: the callbacks aren't retried and their answer carries nothing.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
Member
|
reviewed |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Twilio's debugger logs warning 15003 ("Got HTTP 502 response to https://.../twilio/voice/status") on every call. Our endpoint ran fine and answered 200 in 20 ms. Twilio's own record of the request shows why it counted it as a failure:
x-twilio-reason: Empty/Invalid Response from Remote HostOk()answers a 200 with no body and no content type. Twilio wants either 204 with no body, or TwiML.What changed
The call status (
twilio/voice/status), recording status (twilio/record/status) and transcription (twilio/transcribe) callbacks now returnNoContent(). Nothing else changes: these callbacks aren't retried, and their answer carries nothing.Tests
BotSharp.Plugin.Twiliobuilds.🤖 Generated with Claude Code