A normal check reports; a blocking check also stops the run. With @dg.asset_check(asset=transactions, blocking=True), if the check fails with ERROR severity, the assets downstream of transactions in the same run are not executed and the run fails. The bad materialization is still recorded, so you can inspect what came in, but nothing built on it gets refreshed.
That is the right trade for numbers people act on: a stale dashboard with yesterday's correct totals beats a fresh one with doubled revenue. A WARN result never blocks, even on a blocking check.
When a blocking check fires, fix the data or the asset, then rerun: from the failed run, Re-execute from failure reruns the blocked steps once the upstream is fixed.
If ids repeat, assets downstream of transactions do not run.