# Introducing longer retry windows for batch eligibility checks

> Use the new maxRetryHours property of the Batch Eligibility Check API endpoint to change how long Stedi retries failed checks in a batch.

Published Nov 26, 2025

Updated Nov 11, 2026

Product: Eligibility checks

Note

You can now also set a retry window for batch checks you submit through CSV upload. See [Introducing longer retry windows for batch CSV eligibility checks](https://www.stedi.com/changelog/introducing-longer-retry-windows-for-batch-csv-eligibility-checks).

You can now change how long Stedi retries failed checks in a batch using the new `maxRetryHours` property of the [Batch Eligibility Check API endpoint](https://www.stedi.com/docs/healthcare/api-reference/post-healthcare-batch-eligibility).

You can set any integer between 8 and 24 hours (inclusive). If you don’t specify a value, the default remains 8 hours.

For example:

```bash
curl --request POST \
  --url https://manager.us.stedi.com/2024-04-01/eligibility-manager/batch-eligibility \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '{
  "items": [
    ...
  ],
  "maxRetryHours": 24  // Retry failed checks for up to 24 hours
}'
```

**Note:** You can only set a customer retry window for batch eligibility checks submitted using the [Batch Eligibility Check API endpoint](https://www.stedi.com/docs/healthcare/api-reference/post-healthcare-batch-eligibility).

For more details, see our [announcement blog](https://www.stedi.com/blog/introducing-longer-retry-windows-for-batch-eligibility-checks).