# Configure challengers
URL: https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment-settings/challengers-settings.html

> Configure deployments using the Challengers tab to store prediction request data at the row level and replay predictions on a schedule.

# Configure challengers

DataRobot can securely store prediction request data at the row level for deployments (not supported for external model deployments). This setting must be enabled on the Challengers > Settings tab for any deployment using the [Challengers](https://docs.datarobot.com/en/docs/api/dev-learning/python/mlops/challengers.html) tab. In addition to enabling challenger analysis, access to stored prediction request rows enables you to thoroughly audit the predictions and use that data to troubleshoot operational issues. For instance, you can examine the data to understand an anomalous prediction result or why a dataset was malformed.

You may have enabled prediction rows storage during [deployment creation](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/deploy-methods/add-deploy-info.html). During deployment creation, this toggle appears under the [Challenger Analysis](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/deploy-methods/add-deploy-info.html#challenger-analysis) section. Once enabled, prediction requests made for the deployment are collected by DataRobot. Prediction explanations are not stored. Contact your DataRobot representative to learn more about data security, privacy, and retention measures or to discuss prediction auditing needs.

On a deployment's Challengers Settings page, you can configure the following settings to store prediction request data at the row level and replay predictions on a schedule:

> [!NOTE] Important
> Prediction requests are only collected if the prediction data is in a valid data format interpretable by DataRobot, such as CSV or JSON. Failed prediction requests with a valid data format are also collected (i.e., missing input features).

| Field | Description |
| --- | --- |
| Challengers |  |
| Enable prediction row storage | Enables prediction data storage, a setting required to score predictions made by challenger and compare performance with the deployed model. |
| Enable challenger analysis | Enables the use of challenger models, allowing you to compare models post-deployment and replace the champion model if necessary. |
| Replay Schedule |  |
| Automatically replay challengers | Enables a recurring, scheduled challenger replay on stored predictions for retraining. |
| Replay time | Displays the selected replay time in UTC. |
| Local replay time | Displays the selected replay time converted to local time. If the selected replay time in UTC results in the replay time on a new day, a warning appears. |
| Frequency / Time | Configures the replay schedule, selecting from the following options: Every hour: Each hour on the selected minute past the hour.Every day: Each day at the selected time.Every week: Each selected day at the selected time.Every month: Each month, on each selected day, at the selected time. The selected days in a month are provided as numbers (1 to 31) in a comma separated list.Every quarter: Each month of a quarter, on each selected day, at the selected time. The selected days in each month are provided as numbers (1 to 31) in a comma separated list.Every year: Each selected month, on each selected day, at the selected time. The selected days in each month are provided as numbers (1 to 31) in a comma separated list. |
| Use advanced scheduler | Configures the replay schedule, entering values for the following advanced options: Minute: A comma-separated list of numbers between 0 and 59 or * for all.Hour: A comma-separated list of numbers between 0 and 23 or * for all.Day of month: A comma-separated list of numbers between 1 and 31 or * for all.Month: A comma-separated list of numbers between 1 and 12 or * for all.Day of week: A comma-separated list of numbers between 0 and 6 or * for all. |

> [!NOTE] Note
> The Time setting applies across all days selected. In other words, you cannot set checks to occur every 12 hours on Saturday and every 2 hours on Monday.

---
