I have a small multi-configuration job to check the status of my nodes, such as disk-free.
This is set to run on all of my nodes (all windows VMs). 

The job has a timeout set of 5 mins with 

• strategy: absolute
• time-out actions: abort the build, fail the build

Over the weekend one of my VMs went down and is 'offline' . I would expect the job to abort with failure status after 5 mins, but it does not. The console log shows:

06:47:55 Configuration Jenkins - Admin checks » WIV9195 is still in the queue: ‘WIV9195’ is offline

And within that configuration it says that the job is still pending. This is 'stuck' at a fixed time, and even after 30 mins, no updates to the console.

I have attached some screenshots and the console log.