Application 2.0 Beta Review - Rerunning Applications

Like rerunning an Evaluation, Journey Applications can be rerun. Common reasons include miskeyed data, frozen files, and data service outages.

Rerunning lets you correct the data used in an Application, or run it again once circumstances have changed — for example, after a frozen file is lifted or a data service outage is resolved.

This article covers rerunning a Journey Application from the Alloy dashboard. To rerun one programmatically, see Rerun a Journey Application via the API in our developer docs.

How to Rerun a Journey Application in Application 2.0

1. From the Application detail view, open the vertical ellipsis menu and select Rerun Application. This reuses the payload from the original Journey Application and creates a new Journey Application in the Application Queue.

The rerun form opens. Make your corrections here. The fields shown depend on how your Journey is configured.

After you submit, the new Application displays an indicator in its header that links back to previous Applications in the chain.

Important Considerations

• A rerun creates a new Application. The new Journey Application is linked to the original through a chain indicator in the Application header.

• Reruns within 30 days use cached data. Journey Applications rerun within 30 days of the original use cached data service responses for their Evaluations. Individual Evaluations that are rerun offer the option to update applicant data and refresh the cache to pull new responses. If the supplied data is changed in a rerun, the cache will not be used.

• To get new data service responses for all Evaluations when creating a Journey Application via the API, set the alloy-refresh-cache header to true.

• Use external_partner_id rather than external_group_id for reruns. Each Journey Application request via the API requires a unique external_group_id. Sending a value that has already been used returns a 409 error, meaning the value has to change every time.

• If you want to store a unique identifier from your own system, use external_partner_id instead. The same value can be sent on any number of API calls.