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

Gradle Community

well, if you already know the name ahead of time, you can check if a task has been registered by looking in `tasks.getNames()` without making it configured

but doing anything with the result seems likely racy to me

Check `tasks.names` and if it is not there use  `tasks.whenTaskAdded`?
But that will effectively disable task configuration avoidance.
You can limit it down to just disabling task configuration avoidance for a specific task type if you know the type by using `tasks.withType&lt;...&gt;().whenTaskAdded`.

right, unfortunately there's nothing like `tasks.names.whenAdded` or `tasks.whenRegistered`, so at least publicly you can't watch for additions without forcing realization of added objects. but as a hack using non-public APIs,
```tasks.withGroovyBuilder {
    "whenElementKnown" {
        println(getProperty("name") to getProperty("type"))
    }
}```
seems to work in Gradle 8.0.1

I added an issue for this <https://github.com/gradle/gradle/issues/23994|Provide lazy API for adding configuration actions to registered tasks without waiting for them to be configured>

You are artificially blowing up the example though, don't you? :wink:
`task.name` already is just the name.
`task.path` is with the path.