Jenkins SCM pipeline doesn't provide any action for when the pipeline script can't be fetched. I only just found out a job (which used to work fine) had been failing for months just because it wasn't able to access its pipeline script from the SCM.

It fails the #1 feature of a CI system: notify me when things go wrong. This is a dealbreaker IMHO in terms of making pipeline jobs usable, and violates basic error handling practices (don't ignore errors).

There should be way to define notification actions for when the "checking out the pipeline script" step fails.

This was using Jenkins 2.138.2 with Pipeline 2.6.