Verification failures are generally failures which verify correctness, e.g., failures caused by test, compilation, linting, etc. Non-verification failures are generally failures related to the build toolchain, e.g., failures caused by dependency resolution, build configuration, etc.

Develocity attempts to classify failures based on context, but it doesn't always classify correctly. By default, most failures are classified as non-verification. By explicitly throwing a VerificationException for verification task failures, the failures will be appropriately classified.

Here is a Build Scan showing the behavior with these changes. You'll notice these Architecture check failures are categorized as verification rather than non-verification, which is the case when you look in the Spring Develocity instance.

See also: https://docs.gradle.com/develocity/failure-classification