When using the Startup Trigger plugin, it takes a few seconds for the startup job to enter the build queue. This becomes a problem when combining it with the Priority Sorter plugin since the existing jobs in the build queue will run on the newly connected node before the startup job has a chance, even with the highest priority.

When the node goes online in Jenkins, I'd expect the startup job to enter the build queue immediately, before any jobs have a chance to execute on the new node.