We have limits in place at scans.gradle.com regarding:
- the total size of the build scan
- individual parts of this data
When such limits are reached, scans.gradle.com rejects the build scan, and you see ‘Your build scan could not be displayed’ when you try to access the build scan.
We plan to improve the user experience here, by providing more information when that happens, but I can’t commit to any date yet.
Please note that when using a licensed Gradle Enterprise instance, these limits are configurable to suit your needs.
Also, we optimized the storage of some captured build scan data in recent Gradle Enterprise Gradle plugin versions, and some builds that were exhibiting these symptoms with older version of the plugin will now work fine. Could you upgrade to a more recent version of the plugin and try ?
If it still fails, you can also give me the build scan URL and I will look exactly which type of data is causing the problem, to give you more context.
It is also possible that this message is shown when there is a genuine error processing the build scan data, but I can’t know for sure unless you give me a build scan URL.