Replies: 2 comments
-
|
This sometimes happens due to temporary delays in the GitHub Actions cache service. Even if the upload step reports a timeout or cancellation, the cache may still be saved successfully, which is why the next run can restore it without problems. If rerunning the workflow consistently restores the cache, it is likely a transient issue with the cache backend or network latency rather than a problem with your action configuration. You may also try increasing timeout settings (if applicable) or checking the GitHub Status page to see if there were any incidents affecting Actions or cache services at that time. |
Beta Was this translation helpful? Give feedback.
-
|
This can sometimes happen due to temporary delays in the GitHub Actions cache service. Even if the step reports a timeout or cancellation, the cache may still be uploaded successfully, which is why a rerun is able to restore it. If rerunning the workflow consistently restores the cache, it’s likely a transient backend or network latency issue rather than a configuration problem in your action. You might also want to check the GitHub Status page for any incidents related to Actions or caching around the time the workflow ran. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I have a custom github action that uses the cache@v3 action to save some files to cache.
However, since today, it seems like saving the cache sometimes times out after two minutes! If I restart the action, my action works just fine, because it hits the cache. So even though the operation seems to fail on saving the cache, apparently it does actually save the cache?
As far as I can see the @V3 action also uses the new, non-deprecated cache API.
Could it be that githubs cache endpoints are a bit slow today?
Beta Was this translation helpful? Give feedback.
All reactions