What's the point of a queue (non-intuitive additional steps)

Just a little frustrated. I setup 6 jobs the past evening, I can't recall doing batch work before in resolve. However every other NLE I've used, once multiple jobs are in a queue, they will all be processed when render starts. In resolve, there is no "render all" button, just start render...It took a wasted overnight and now a delay to realize you have to select everything in the queue and then hit render.

I'm sure it's in the manual, however I would think anyone coming from moderate experience with an NLE would likely assume the act of adding a job to the queue alone would schedule it for being processed in conjunction with everything on the queue.

Anyway, just a thought, was surprised and now have another day delayed.

[Peter Chamberlain]

The render queue will render the selected job if one is selected, and all if none or all are selected.

And I think it's logical, since may need one of the jobs immediately and don't want to kill the others first.

Well, the last added render is always automatically selected, so it's very easy to make this mistake.

If there was an option to not have that happen, and a possibility to drag items in the queue to reorder them, I would use that instead, together with a "Render non-rendered items" button.

Well, the last added render is always automatically selected, so it's very easy to make this mistake.

True, and I think this happened to the OP.
I think no job should ever be selected by default, because if selecting a job was an opt-in option only, 100% of mistakes would be avoided.
Another mistake I made once a few years ago was to add jobs with the same name for the exported file, so Resolve exported 4 jobs - overwriting the previous ones - ending in only one in hte end (maybe that's fixed now, just a basic message would be enough).

OK, right, I second that none should be selected by default.