## The symptom

After updating turbo from 1.10.16 to 1.11.0, every turbo command prints:

```
WARNING artifact verification failed: Error making HTTP request: HTTP status
client error (401 Unauthorized)
```

The reporter used a self-hosted remote cache with `TURBO_TOKEN` set in the
root `.env` file, and it had worked without warnings before the update. Another
reporter found the same warning is reliably triggered when a `remoteCache`
section is configured in `turbo.json`, in which case the `TURBO_TOKEN` env
variable appears to be ignored.

## The fix

1. Regenerate your token and make sure its scope covers the team that owns the
   remote cache. The original reporter fixed the warning by creating a new
   Vercel token with the correct team scope.
2. If you set a `remoteCache` section in `turbo.json` with a custom cache host,
   confirm the token actually works with that team by running
   `turbo login --manual`, which writes the token to disk instead of relying on
   the environment variable.

## Also worth doing

The Turborepo team improved the error messages for this path in PR #12314, so
upgrading past that change gives a clearer diagnosis than the bare 401 warning.

## The general lesson

A 401 that appears after a version bump with an unchanged token is usually a
scope or delivery problem (wrong team scope, env var no longer read), not a
wrong secret. Verify the token's scope before rotating it blindly.