Great Expectations "Checkpoint ... not found" / validation failed in CI

Great Expectations loads checkpoints and expectation suites from the data context. When the named checkpoint or suite is not on the runner, it raises a not-found error; when the data violates the suite, the run returns success: false and the step fails.

What this error means

A GE step fails with "great_expectations.exceptions.CheckpointNotFoundError: Checkpoint X was not found" / a missing expectation suite, or the validation result reports "success": false and the job exits non-zero.

great_expectations.exceptions.exceptions.CheckpointNotFoundError:
Checkpoint `daily_checkpoint` was not found.

Common causes

The checkpoint or suite is not in the context on the runner

The great_expectations/ directory (checkpoints, expectations) was not checked out or the context root points elsewhere in CI.

The data genuinely violates the suite

The checkpoint runs but one or more expectations fail, so the result is "success": false and the step is expected to fail.

How to fix it

Point the context at the committed GE project

1. Ensure the great_expectations/ directory is in the checkout.
2. Initialize the context at that root so checkpoints and suites are discovered.
3. List checkpoints to confirm the name resolves.

import great_expectations as gx
context = gx.get_context(context_root_dir="great_expectations")
context.list_checkpoints()

Read the validation result for real failures

When the checkpoint runs but fails, inspect the result to see which expectation failed and fix the data or the expectation.

result = context.run_checkpoint(checkpoint_name="daily_checkpoint")
assert result["success"], result

How to prevent it

• Commit the full great_expectations/ project and check it out in CI.
• Set the context root explicitly so names resolve.
• Treat "success": false as a real data-quality failure to investigate.

Related guides