This instance of jenkins I'm running has a bunch of remote nodes that are configured to be launched on demand and taken offline when no jobs are using them.
I also have some recurring jobs that are attached to specific nodes.

I noticed that when I put jenkins in quietDown mode, and then those jobs tied to remote nodes are triggered, jenkins still launches the agent and keep the node online, even if it's not going to actually start the jobs due to being in quietDown.

IMHO, slaves that are configured to stay down until requested shouldn't be started when in quietDown, but rather brought up once quietDown has been cancelled.