From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

I guess you mean "tasks which were _created_ but not _executed_". In that case I don't think there's an obvious list. We usually recommend that builds try to minimize the number of tasks `Created during configuration` , which is <https://ge.gradle.org/s/777upuhlnwyua/performance/configuration#summary-tasks-created-during-configuration|displayed in the Build Scan>.
AFAIK there's no simple way to get a list of all of these tasks in a Build Scan: you can see the ones created during Plugin application <https://ge.gradle.org/s/777upuhlnwyua/performance/configuration?details=code-unit-org.gradle.docs.samples.internal.samplesdocumentationplugin!:docs&amp;openScriptsAndPlugins=WyJjb2RlLXVuaXQtb3JnLmdyYWRsZS5kb2NzLnNhbXBsZXMuaW50ZXJuYWwuc2FtcGxlc2RvY3VtZW50YXRpb25wbHVnaW4iXQ|like this>, but I don't think we capture tasks created by a build script directly.

I guess a task must be created in order to be configured, so reducing the number of created tasks is probably your best bet.

hey Daz! Yes, I meant created. Basically I'd like to hunt redundant configuration. Would be nice to have a view which simply lists that: given an invocation, there are tasks which are created, but some would never be executed.

Yep, I think logging is the only way to work this out. It can be worthwhile to run something like `gradle help` and eliminate all other task creation.

Probably similar to this <https://gradle-community.slack.com/archives/CDB9Q0MPT/p1658241741643549>?