That is how it works. When you do 'run all', the cells after the error are skipped.

When you do run all below, they all get executed (and mostly throw an error).

Databricks probably has a reason for this behavior. The notebook experience is not bad but certainly not perfect.