It seems that if Jenkins fails to shut down correctly and resume is disabled by user it can put a job in a limbo state, where it is both failed and still running.

Image 1:

As you can see in this image the job is marked as failed but the dots at the bottom show Jenkins is still waiting for more from the job.

Image 2:

As you can see from the second image there is no ability to delete or abort the job either.

Image 3:

As you can see from this image a further job is waiting in the queue because it still thinks this one is running despite it not running.

It likely has something to do with the durability settings as the pipeline durability setting is set to Performance Optimized and the job is set not to resume. It could also have something to do with the custom SCM plugin I'm using (but seeing as this job hasn't started the checkout yet I'd be a little surprised).

I suspect if I restarted Jenkins it would fix it, but I haven't done that yet and would prefer not to. A solution I have employed is to change the job configuration to abort running jobs (which allows the waiting build to start) and then turn that setting back off afterwards (but this is also rather annoying, especially when multiple jobs end up in this state).

This is my first ticket so sorry if I've not created this correctly!