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

Gradle Community

What is the Dataflow Actions docs section <https://docs.gradle.org/9.1.0/userguide/dataflow_actions.html#using_lifecycle_event_providers|Using lifecycle event providers> supposed to be demonstrating? A <https://docs.gradle.org/current/javadoc/org/gradle/api/flow/BuildWorkResult.html|BuildWorkResult> doesn't contain `buildInvocationId`, `workspaceId`, or `userId` - just `getFailure()`.

And this sentence doesn't make sense to me

> Besides the usual value providers, Gradle provides dedicated providers for build lifecycle events, like build completion
What are 'usual value providers'? And I don't see any 'dedicated providers' - just a single one: `getBuildWorkResult()`.

And it's not exactly clear what this is. The Javadoc says "Summary result of the execution of the work scheduled for the current build", but there's no summary, just a Throwable. Is the 'execution of work' per task? Or for <https://docs.gradle.org/current/userguide/glossary.html#b|a build>?

The plural is probably seeing into the future, or there were multiple planned not only one made it into the first version 

So yes, the build work result is the only such dedicated provider right now. And the three IDs you wondered about are actually irrelevant. They are taken from a field named `scopeIdsService` which probably is another injected service. 

The provider is just used for the mentioned ordering guarantees and then `map`ed to a `Map`.