Cache Init Failed

[restive osprey]

For a few weeks I've noticed that our dagger engines weren't pulling cache volumes down from magicache on startup. I finally found some time to look into it and discovered this engine log:
time="2025-06-04T07:48:10Z" level=debug msg="using cache service at https://api.dagger.cloud/magicache"
time="2025-06-04T07:48:10Z" level=warning msg="cache init failed, falling back to local cache" error="unexpected status code: 404: "
I tried again with a fresh DAGGER_CLOUD_TOKEN, but the error persists. We're on v0.18.7.

[half thistle]

hey @restive osprey. We're looking into this. We'll get back to you in a bit. Question, are you using the dagger + depot integration by any chance?

[restive osprey]

Thanks! We aren't using depot, nope.

[half thistle]

gotcha thx. Just saw an internal message that we'll be pinging you privately about this 🙏

[maiden trail]

Hi, sorry to jump into the conversation, may i know what was the solution to this?

because im also getting the same error from the dagger engine log

time="2025-07-18T01:41:30Z" level=debug msg="using cache service at https://api.dagger.cloud/magicache"
time="2025-07-18T01:41:31Z" level=warning msg="cache init failed, falling back to local cache" error="unexpected status code: 404: "
time="2025-07-18T01:41:31Z" level=debug msg="starting optional cache mount synchronization"
time="2025-07-18T01:41:31Z" level=debug msg="starting main engine api listeners"
time="2025-07-18T01:41:31Z" level=info msg="running server on /run/buildkit/buildkitd.sock"
time="2025-07-18T01:41:31Z" level=info msg="running server on /run/dagger/engine.sock"

and also could this be the reason why all my cache volumes just dont get persisted across github action runs (when im already using dagger cloud)?

[half thistle]

cc @naive dragon