I initially suspected actions/setup-node needed updating to enable the segment timeout added in actions/cache@v3.0.8.

Upon closer inspection, actions/setup-node uses a version of actions/cache with a default timeout of 60 minutes, not 10 minutes.

As a workaround, I've set a much shorter timeout; I'll report back here if I encounter any further problems 😛

env:
  # https://github.com/actions/cache/blob/04f198bf0b2a39f7230a4304bf07747a0bddf146/tips-and-workarounds.md#cache-segment-restore-timeout
  # -- note that actions/setup-node@3 [uses actions/cache@3.0.4](https://github.com/actions/setup-node/blob/a4fcaaf314b117a40d694a35ee36461f8ff3c6e6/package-lock.json#L41)
  #    which has a [default timeout of 60 minutes](https://github.com/actions/toolkit/blob/457303960f03375db6f033e214b9f90d79c3fe5c/packages/cache/RELEASES.md#304),
  #    not 10 minutes! Let's reduce it further.
  SEGMENT_DOWNLOAD_TIMEOUT_MINS: 2

Hello @bennettp123!
Thank you for reporting this! We will investigate the issue

We're also experiencing this issue. Disabling the yarn cache fixed our builds temporarily but we'll try this.

Same here, we encounter this frequently https://github.com/prisma/prisma/actions/runs/4746282641/jobs/8429723075#step:9:438

Related #726

Hello @bennettp123,

The default timeout has been reduced to 10 minutes. Could you please verify on your end if this resolves the issue? If not, kindly provide the reproduction steps. For reference, you can review the changes made in the options.ts file

Hello @bennettp123,

Just a quick reminder to check if the issue has been resolved. Please let me know if there's anything else I can assist with!

Hello @bennettp123, We will be closing this issue for the time being due to lack of recent communication. However, please don't hesitate to reach out if you have any further questions or concerns, and we’ll be happy to reopen the issue as needed.