great expectations checkpoint failed error "action list contains unknown action class"

TL;DR

Remove or replace the unknown action in the checkpoint config: the action list names a class that this Great Expectations version cannot import, usually a removed legacy action or a custom action whose package is not installed. Checkpoint actions run after validation. An action class that fails to import stops the checkpoint even when every expectation passed, because the checkpoint cannot build its action list.

great expectations checkpoint failed error "action list contains unknown action class"

Use this when

• The check or run fails with this symptom: a Great Expectations checkpoint fails with action list contains unknown action class.
• You are working on a Great Expectations checkpoint upgraded across versions or moved to a new environment 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 checkpoint that fails during validation itself, where the action list is never reached.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Read the error for the exact class path it cannot resolve. Verify: the unknown action class is named
2. Check the installed Great Expectations version and whether that class still exists in it. Verify: a removed or renamed class is confirmed, or a missing custom package is found
3. Replace the action with the current equivalent, such as the updated store or update-data-docs actions, or install and register the custom action package. Verify: the checkpoint config references only importable classes
4. Run the checkpoint on a small batch. Verify: validation completes and the configured actions execute
5. Run the same config in the deployment environment, not only locally. Verify: the action list resolves there too

Variant phrasings

great expectations action list contains unknown action class

The shorter phrasing focused on the named failure.

checkpoint failed unknown action class great expectations

The symptom phrasing a searcher tries next.

great expectations checkpoint action class fix

The variant naming the failing stage or tool directly.

Compatibility: Great Expectations 0.18 and 1.x checkpoint configurations

Why it happens

Legacy checkpoints carried action classes that were renamed or removed in later releases, and custom actions live in separate packages. Moving a config between versions or environments without the matching package makes the class unknown at checkpoint build time.

Edge cases / pitfalls

• Store validation result and update data docs actions changed names across versions; copy action blocks from a config generated by your installed version.
• An action that imports fine locally can still fail in a container that skips optional dependencies; pin the environment, not just the config.

Provenance

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

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

Thread query: great expectations checkpoint failed error "action list contains unknown action class"

TL;DR: Remove or replace the unknown action in the checkpoint config: the action list names a class that this Great Expectations version cannot import, usually a removed legacy action or a custom action whose package is not installed. Checkpoint actions run after validation. An action class that fails to import stops the checkpoint even when every expectation passed, because the checkpoint cannot build its action list.