NX build issues with a restored cache from Github Actions

[marellak36]

Hello,
I'm new to NX and seeking recommendations for optimizing our monorepo CI. We have NodeJS and Java packages, use GitHub Actions with managed runners, and are experiencing intermittent failures with actions/cache@v4. Specifically, we're seeing below error. What's the recommended approach for reliable caching in this setup?" My subsequent jobs are running at times, but intermittently nx build is failing due to below error. Thought it might be due to managed runners but error is not happening all the time.

My GHA logic to save cache:
.nx/cache
key: ${{ github.event.repository.name }}-dev-nx-cache-${{ github.sha }}
restore-keys: |
${{ github.event.repository.name }}-dev-nx-cache-

The local cache artifact in "****/.nx/cache/80262457583648894**" was not generated on this machine.
As a result, the cache's content integrity cannot be confirmed, which may make cache restoration potentially unsafe.
If your machine ID has changed since the artifact was cached, run "nx reset" to fix this issue.
Read about the error and how to address it here: https://nx.dev/troubleshooting/unknown-local-cache"

If i read through the documentation suggestion is to use a "NX_REJECT_UNKNOWN_LOCAL_CACHE=0." How safe is this in the context of NX to use above for prod workflow to speed up builds ?