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

Gradle Community

Fix:
• If you are using cradle enterprise you can just remove that entry
• Purge the cache seems a little drastic, but would work
• You can run the task with --rerun-tasks so it doesn't use the cached artifact..but I wonder if it would override the corrupted one

`--rerun-tasks` will push to cache on success just like a normal build would. So it will overwrite the remote cache only of configured to push there.

it seems fixed. Thanks a lot guys for response :bow:

by the way it happen again, even after i purge the cache somehow build still produce corrupted cache. Is there any known issue about it or anything I can do to troubleshoot this ? Currently seems i need to disable cache on this task, but not sure why this corrupted.

not sure recently lot of cache failed
&gt; Build cache entry 9fe056a89ac28b7188d6b61d2640dd20 from remote build cache is invalid
  &gt; Failed to read Paxheader. Encountered a non-number while reading length
    &gt; Failed to read Paxheader. Encountered a non-number while reading length

how we can troubleshot this kind of issue ?

If you are using Gradle Enterprise I would open a zendesk issue, it probably needs some investigation