Thank you !

That's very helpful, and an impressive exercise in inductive reasoning :-)

The four words defining stalled projects in the help file ("without any available actions") probably do need a bit of expansion. They don't reveal much of what the filter really does, let alone of the distinction between it and the applescript library's number of available tasks is 0

Your draft query already reveals much more, and I am empirically getting the same results as stalled (in my database, and this morning's build of OF 1.8) by expanding your search to include active projects which simply lack any kind of task at all, and restricting it to exclude singleton holders. Thus, in applescript, the fairly baroque:

projects where status is active and ((number of tasks is 0) or ((its number of tasks > its number of completed tasks) and (its number of available tasks is 0))) and singleton action holder is false and ((hidden of its folder is false) or (its folder is missing value))

or in English, for the help file, something like:

"Active projects which have no tasks, or which have remaining tasks which are unavailable. (Does not include empty single action lists, or projects in dropped folders)."

I can see the value of the 'stalled' filter, and I might be more inclined to make use of it now that (I think) I understand it, but I suspect that I will personally be sticking with simpler and clearer filters for my own day to day work :-)

--