---
title: Redrive AWS Step Functions executions
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: >-
  Docs > Serverless > Serverless Monitoring for AWS Step Functions > Redrive AWS
  Step Functions executions
---

# Redrive AWS Step Functions executions

This page explains how to [redrive](https://docs.aws.amazon.com/step-functions/latest/dg/redrive-executions.html) executions directly from Datadog to continue failed AWS Step Functions from the point of failure without a state machine restart.

{% image
   source="https://docs.dd-static.net/images/serverless/step_functions/redrive_2.0c93aa9ede04342614a22cc249ff1926.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/serverless/step_functions/redrive_2.0c93aa9ede04342614a22cc249ff1926.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="A visualization of a failed Step Function execution." /%}

## Enable redrive within Datadog{% #enable-redrive-within-datadog %}

To enable using redrive within Datadog, configure an [AWS Connection](https://docs.aws.amazon.com/dtconsole/latest/userguide/welcome-connections.html) with [Datadog App Builder](https://docs.datadoghq.com/actions/app_builder.md). Ensure that your IAM roles include permissions that allow executing a Step Function for the retry action (`StartExecution`) or redriving a Step Function for the redrive action (`RedriveExecution`).

## Usage{% #usage %}

To take action on a Step Function in Datadog:

1. Go to the [Step Functions](https://app.datadoghq.com/functions?cloud=aws&entity_view=step_functions) page.
1. Find the Step Function you wish to redrive.
1. Open this Step Function's side panel. On the Executions tab, locate the failed execution you wish to redrive.
1. Click on the Failed pill to open a redrive modal.
1. Click the Redrive button.

## Tracing redrives{% #tracing-redrives %}

When monitoring redriven executions, use the Waterfall view, as the large gap between the original execution and redrive can make the Flame Graph view imperceptible.

### Troubleshooting missing redrive traces{% #troubleshooting-missing-redrive-traces %}

A redrive may not always share the same sampling decision as the original execution. To ensure that the redriven execution is also sampled, you can reference the `@redrive:true` span tag in a retention query.

## Further Reading{% #further-reading %}

- [Restarting state machine executions with redrive in Step Functions](https://docs.aws.amazon.com/step-functions/latest/dg/redrive-executions.html)
- [Datadog App Builder](https://docs.datadoghq.com/actions/app_builder.md)