Application Queue: Rerun Applications

Similar to rerunning evaluations in Alloy, Journey Applications can also be rerun. Reasons for rerunning both evaluations and Journey Applications can include miskeys, frozen files, and data service outages. The idea is to correct the data used in the evaluation or Journey Application or run them again when circumstances have changed, like in the event of a frozen file being lifted or data service outage being resolved. While this article documents how to rerun a Journey Application from the Alloy dashboard, our developer docs detail how to rerun a Journey Application via the API.

How to Rerun a Journey Application in the Alloy Dashboard

1. From the Application Queue, access a Journey Application that needs to be rerun.
2. In the upper right corner of the Journey Application page, click the button with the three dots, then click Rerun Application.
   1. 
   2. This uses the same payload as the original Journey Application, and creates a new Journey Application in the Application Queue.

Important Considerations

• The Rerun Application feature creates a new Journey Application that will not be linked to the original in Alloy.
• Specific evaluations within a Journey Application can also be rerun. Note that a Journey Application will not “resume” after rerunning an evaluation within it. After rerunning an evaluation within a Journey Application, the following note will appear at the top of the new evaluation:
  • “This evaluation is for review purposes only. The new outcome does not affect the application.”
  • Agents can use the outcome of the new evaluation informationally in their manual review process.
  • To rerun an evaluation within a Journey Application:
    • Access the evaluation. Then, in the upper right corner, click the three dots and select Rerun Evaluation.
      • 
• Journey Applications that are rerun within 30 days of the original will return cached data service responses for the evaluations within. Evaluations within a Journey Application that are rerun offer the option to update applicant data and refresh the cache to receive new data service responses.
  • Use the alloy-refresh-cache header set to true when creating a Journey Application via API to get new data service responses for all evaluations.
• When creating a Journey Application via the API, each separate request requires a unique external_group_id. Clients typically use this field to match a unique identifier in their external system for the application. A 409 error will be returned for the API call if clients try to send an external_group_id that has already been used. This field does not work well in a rerun scenario because the value has to be changed. Clients can alternatively use the external_partner_id field to store the unique identifier from their external system for the application. The same value can be sent for this field for any number of API calls.