---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/84002#article
headline: "84002: Workflow execution failed. "
url: https://www.twilio.com/docs/api/errors/84002
inLanguage: en
dateModified: 2026-06-09T11:00:42.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 84002: Workflow execution failed. 

Log Type: APPLICATION

Log Level: ERROR

## Description

This error means a Studio Flow Execution failed before it could complete. Review the Execution log to identify the failed widget, inspect the Step event, and use the Debugging Information and Flow Data panels to find the specific runtime failure.

### Possible causes

* A downstream exception occurred while the Flow was running.
* A `Run Function` widget did not return successfully. This can happen if the Function returns a `4xx` or `5xx` status code, takes longer than 10 seconds, or returns a response body larger than 64 KB.
* A `Make HTTP Request` widget failed because the endpoint did not return a successful response, timed out after 10 seconds, or returned a response body larger than 64 KB.
* A message or call operation failed in a widget, which caused the Execution to end before later widgets were reached.

### Possible solutions

* Open the Flow's Logs, find the failed Execution by contact address and time range, and inspect the failed Step's Debugging Information to identify the exact widget and error details. If needed, review Flow Data for the full execution state.
* If the failure came from `Run Function`, make sure the Function returns a `2xx` or `3xx` response within 10 seconds and keeps the response body under 64 KB. Return valid JSON when you want Studio to parse the response into variables.
* If the failure came from `Make HTTP Request`, verify the Request URL, request settings, and downstream endpoint behavior. Make sure the endpoint returns a `2xx` response within 10 seconds and keeps the response body under 64 KB. If you need to send custom headers, use a Function to make the request instead.
* Add or review failure handling transitions in the affected widget so the Flow can move to a recovery step when a downstream request fails. For repeated downstream failures, track retry attempts with a variable and branch after a fixed number of retries instead of looping indefinitely.
* If the issue started after a recent Flow change, review Revision History to identify the change that introduced the failure and revert to an earlier revision if necessary.

#### Additional resources

* [Studio Troubleshooting](/docs/studio/user-guide/studio-troubleshooting)
* [Run Function widget](/docs/studio/widget-library/run-function)
* [Make HTTP Request widget](/docs/studio/widget-library/http-request)