Recover a quarantined result
Put a good materialization back on latest.
A quarantined materialization is stored, and readers should not use it. puppi assets prints quarantined next to the staleness state. puppi assets <key> names the check that failed. The rules for the check itself are in Quarantine.
There are two ways a result gets there, and the recovery is different for each.
A check failed during a run
The rows were written, the materialization was stored, and latest stayed on the previous result. The attempt status is failed_by_check. Its error_class is terminal, and the message starts with check failed:. Assets later in that run are blocked.
Fix the producer or the data, deploy if the code changed, and run again:
puppi deploy --env hello
puppi run --wait --env hello The quarantined row stays in the history.
A deploy quarantined the current result
Activating a deployment re-checks every declared schema against the columns stored on the current latest. No asset runs. When the stored columns no longer match, that materialization is marked quarantined while it is still latest.
Point the environment at the previous deployment. Activation runs the check again, and clears the quarantine when the stored columns match the restored schema. The commands are in Roll back a deployment.
On a strict environment, a later deploy that changes the declared schema has to name the asset:
puppi deploy --env hello --allow-contract-change core/customer Point latest at an older copy
puppi rollback core/customer --env hello
puppi rollback core/customer --env hello --to <materialization-id> What puppi rollback accepts and refuses is in Deploy and rollback.