Clear up that container queries use the first step's name as an unique de-duplication identifier. I would love to see some comments around this, since it was not clear to me (until I worked on fixing issues with it..)

I would also like to allow some queries to be duplicated, like tracking. You may track c quest, then b quest, then c quest again. But you should not allow multiple content book analysis in a queue...

I am pretty certain that is in fact documented. ;-) But I know, it's hard to read the documentation. And it might not be the best way to achieve the de-dup functionality.

Might be the case. I still want to add an "allow duplicate in queue" flag for the queries.

I am pretty certain that is in fact documented. ;-) But I know, it's hard to read the documentation. And it might not be the best way to achieve the de-dup functionality.

Sure, that sounds fine.