80502: Internal Server Error from Downstream

Twilio returns this error when Proxy sends a request to a downstream service and that service fails or refuses to process it. Review the matching Debugger event to confirm which Proxy request failed and whether related notifications provide more detail.

• A downstream service returned an internal server error while Proxy was processing your request.
• A downstream service refused the request that Proxy sent on your behalf.
• The root cause was emitted by a related downstream system and is only visible in associated Debugger events.

• Open the Twilio Console Debugger and review the 80502 event, including the Log Properties and any related notifications for the same request.
• Identify which Proxy operation failed, such as a request involving a Service, Session, Participant, or Interaction resource, then retry only after you have confirmed the failure details.
• If the error continues, capture the Twilio-Request-Id response header, note the timestamp and affected resource SID, and contact Twilio Support.
• If your application retries failed API requests, use exponential backoff to avoid adding more load while you investigate.

• Proxy API overview
• Twilio Debugger
• API best practices