This message was deleted.

You could just use

tasks.configureEach { ... }

and action will be executed when task is realized. If you collect realized task names from the action and compare them to

tasks.names

you should have actual list at the action execution time I think

Differently asked, what do you actually want to achieve, what is your use-case? It sounds like you chose a solution for a use-case and wonder how to fix it, but there might be a better solution if you take a step back.

My use case is working fine, I'm basically wondering why there is no lazy equivalent of

#maybeCreate

I guess because that method is supporting odering constraints which is bad. If plugin A is applied first, task x is variant X, if plugin B is applied first, task x is variant Y, for example.