# Error checking storage: AccessDenied: Access Denied

**URL:** <https://discuss.circleci.com/t/error-checking-storage-accessdenied-access-denied/44816>\
**Category:** Caching Dependencies\
**Created:** [July 25, 2022, 5:48pm UTC](https://discuss.circleci.com/t/error-checking-storage-accessdenied-access-denied/44816 "2022-07-25T17:48:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![fmorency](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/fmorency/32/30673_2.png) [@fmorency](https://discuss.circleci.com/u/fmorency)\
**Post date:** [July 25, 2022, 5:48pm UTC](https://discuss.circleci.com/t/error-checking-storage-accessdenied-access-denied/44816/1 "2022-07-25T17:48:08Z")

</div>

A new cache error happened today in the `Restore Cache` step

```auto
skipping cache - error checking storage: AccessDenied: Access Denied

```

We recently enabled the `Pass secrets to builds from forked pull requests` to enable cache sharing.

Cache saving in the same pipeline worked.

Cache worked as expected before.

Any idea what’s causing this issue? We’re on the Performance paid plan.

Thanks!  
-F

---

<div class="post-metadata">

**Author:** ![fmorency](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/fmorency/32/30673_2.png) [@fmorency](https://discuss.circleci.com/u/fmorency)\
**Post date:** [July 26, 2022, 2:41pm UTC](https://discuss.circleci.com/t/error-checking-storage-accessdenied-access-denied/44816/2 "2022-07-26T14:41:23Z")

</div>

It seems it was only a glitch from enabling the cache sharing option.

Complete your job until a “new” cache is saved if this issue happens to you. Then things should start working again.

---

<div class="post-metadata">

**Author:** ![fmorency](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/fmorency/32/30673_2.png) [@fmorency](https://discuss.circleci.com/u/fmorency)\
**Post date:** [August 3, 2022, 1:24pm UTC](https://discuss.circleci.com/t/error-checking-storage-accessdenied-access-denied/44816/3 "2022-08-03T13:24:20Z")

</div>

After speaking with support, this is a CircleCI issue that has been escalated to Engineering. CircleCI should fix it at some point.
