Hi,

Today, we have experienced above cache step failure reason almost always with the following case:

• Workflow runs on a self-hosted runner that has a slow upload rate (~4Mbits per sec)
• Cached content is large (~80MB tar)

This makes cache action pretty unreliable. We would be ok for very slow cache uploads, but getting 503 makes our workflows very hard to optimize.

Is this a known issue that GitHub team is actually working on? There are #154 and #200 , but I didn't see a progress on any of them.

Thanks!