---
updatedAt: 2026-06-17T20:17:33.000Z
agentTools:
  projectIndex: https://developer.alloy.com/public/llms.txt
---

# Rerunning Journey Applications

In certain cases, you may want to rerun a particular Journey Application in order to retrieve an updated or corrected outcome; for example, if the application terminated in an `error` status due to a Journey misconfiguration, or if one of the data vendors in an underlying workflow fails to execute.

## Initiating a Rerun

You can initiate a rerun for a Journey Application either through the Application Queue dashboard or via the [Rerun Journey Application](https://developer.alloy.com/public/reference/post_journeys-journey-token-applications-journey-application-token-rerun) endpoint. When a rerun is initiated, Alloy will generate a `started_rerun_application` event for the original Journey Application, which is sent [via webhook](https://developer.alloy.com/public/docs/webhooks-example-payloads#journey-status-change-events) and appended to the `_embedded.events[]` array in the API response:

```json _embedded.events

{
    "_embedded": {
        ...
        "events": [
            ...
            {
                "journey_application_event_token": "22752065",
                "journey_application_token": "JA-8amRtBU3M98EWa4Hq8j7",
                "type": "started_rerun_application",
                "timestamp": 1691764389137,
                "entity_token": null,
                "entity_application_token": null,
                "rerun_journey_application_token": "JA-XnOSwyRTCqgrj6dNvCBw",
                "_embedded": {
                    "node": {
                        "id": null,
                        "name": null,
                        "type": null
                    }
                },
                "_links": {}
            }
        ],
    }
}
```

## Linking Reruns back to Root and Previous Journey Applications

If a Journey Application is created via rerun, the API response will contain data about where the Journey Application originated from in the `_embedded.rerun` section:

```json _embedded.rerun
{  
    ...  
    "_embedded": {  
        "rerun": {  
            "initiated_by": "api",  
            "previous_journey_application_token": "JA-8amRtBU3M98EWa4Hq8j7",  
            "root_external_group_id": "8331a098-4238-4e26-bbdf-9a5a103ce509",  
            "root_journey_application_token": "JA-8amRtBU3M98EWa4Hq8j7"  
        },  
        ...  
    }  
}
```

If multiple reruns are initiated from the same Journey Application in a chain, the `previous_` Journey Application fields will reference the source Journey Application from which the rerun directly originated from. The `root_` Journey Application fields will always reference the first Journey Application in the chain, before any reruns were initiated. Similarly, the `started_rerun_application` webhook/event will be appended to both the previous **and** root Journey Applications.

If there's only one rerun in the chain, the previous and root Journey Application will be the same.