Prior to running the selection tree, the manager.state.desired_job_list contains the correct order. This is just the relevant fragment as the djl is originally a bit long: , , , , I selected only the miscellaneous tests in the tree selection, and the tree.selection now has an incorrect order: djl from tree [, , , , , , , , , , , , , , , , ] Then apparently when updating the desired job list, the wrong order seen above is considered: self._update_desired_job_list(manager, tree.selection) after this, the manager.state.desired_job_list contains the bad order: [, , , , , , , , , , , , , , , , ] =========== Note however that this is not 100% reproducible; the following run, I got this from the selection tree: [, , , , , , , , , , , , , , , , ] with that ordering, the actual run did produce the correct results. Once again, running this produced this from the selectiontree, note the relative ordering of the fwts_tests is correct, but submission_resources now snuck in between them: djl from tree [, , , , , , , , , , , , , , , , ]