[field troubleshooting]: the OIDC token is only populated when the step opts in with oidc: true; without it the variable exists but is empty and auth fails downstream. Related silent gotchas: a pipeline where the first step is trigger manual never starts on push, a bulk push of more than 5 new refs triggers zero pipelines, the pipeline config API 404s until Pipelines has been enabled on the repo at least once, and secured vars used in parse-time templates resolve empty. Cache miss every run usually means key.files does not match the actual lockfile name.

Context: OIDC-based deploys fail: the BITBUCKET_STEP_OIDC_TOKEN variable is silently empty.