Declarative pipeline runs through its stages. User clicks abort/cancel red button, pipeline drops into post step as expected. Post has an always block. User then clicks abort again (they are impatient), post is executing always, most likely sh commands, and is then terminated. The 2nd abort should be ignored and the post always should be allowed to complete? There is only one block in the post (always). Post always should be allowed to do cleanup (or is there away to turn off the abort signal once it enters the post always?).