## TL;DR
A batch request that cannot be resolved means the datasource, data connector, or batch identifiers do not line up: print the available batches from the datasource, compare the batch identifiers and splitter settings with the request, and fix the mismatch in names, regex, or data asset path. The data itself is rarely the problem at this stage.

```text
great expectations error: batch request could not be resolved failed
```

## Use this when
- The check or run fails with this symptom: batch request could not be resolved is raised before validation starts.
- You are working on a Great Expectations setup failing at batch resolution and the failure repeats on the same data or configuration.
- You need the failing rows, rule, or stage isolated before changing thresholds or code.

## Not for this skill when
- A validation failure after the batch loads, which means resolution worked and the data is at fault instead.
- The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

## Steps
1. List the batches the datasource actually returns for the asset, using the datasource's batch listing in a notebook or script. Verify: the real batch identifiers are printed
2. Compare the request's datasource name, data connector name, data asset name, and batch identifiers character by character with the configuration. Verify: every mismatched name or identifier is found
3. If files are involved, test the data connector regex against the real file names in the data directory, including date partition patterns. Verify: the regex matches the actual files or the mismatch is shown
4. Correct the configuration or the request, keeping names in one place so code and YAML cannot drift apart. Verify: the request and configuration agree
5. Rerun the batch request and load the head of the batch to prove resolution, then run the checkpoint. Verify: the batch loads and validation proceeds

## Variant phrasings
### great expectations batch request could not be resolved
The verbatim error phrasing.
### batch request could not be resolved data connector regex
The file-connector phrasing for regex and partition mismatches.
### great expectations fluent datasource batch identifiers
The fluent-API phrasing for listing batches from a datasource.

Compatibility: Great Expectations 0.18 and 1.x fluent and classic datasources

## Why it happens
Batch resolution is a lookup across several named objects and a file or query pattern. A renamed asset, a regex that no longer matches new file names, or options passed in code that override the YAML all make the lookup return nothing, which Great Expectations reports as an unresolvable batch request.

## Edge cases / pitfalls
- An empty data directory produces the same error as a wrong name. Confirm files exist before rewriting configuration.
- Options passed in code silently override YAML. Print the effective datasource configuration when debugging.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_24CAo2tc5yDX9lZpd_o48w