Hello Vercel Support,
we are seeing a reproducible mismatch between the Preview environment configuration returned by Vercel and the values actually injected into a newly created Preview deployment.
Project:
prj_nScKmZiuIpadgtWyDNaDxKy6D0hz
Team:
team_theNPtB9czlLGhrh3K5vlxFM
Affected deployment:
dpl_DEqXN4qggKYMA97DFBTZqmev3NqT
Deployment URL:
ai-orchestrator-rofabb1o0-aivanizki-bits-projects.vercel.app
Git ref:
codex/ledger-hosted-native-preview-003r6-repair-evidence
Git SHA:
be856b765b47401abb3eabdd2766f6b57182b643
The affected variables are:
CHECKOUT_TEST_USER
CHECKOUT_TEST_PASSWORD
A fresh explicit pull from the linked project, team, and preview environment returns the currently configured Preview values.
Non-secret fingerprints:
Fresh Preview configuration:
-
CHECKOUT_TEST_USER: 11 chars / 11 bytes / HMAC prefix885f… -
CHECKOUT_TEST_PASSWORD: 11 chars / 11 bytes / HMAC prefix885f…
However, the newly created READY Preview deployment receives a different pair:
Deployment runtime:
-
CHECKOUT_TEST_USER: 6 chars / 6 bytes / HMAC prefix3aa3… -
CHECKOUT_TEST_PASSWORD: 16 chars / 16 bytes / HMAC prefixc363…
Both environment variables appear as single Preview-only project entries. We found no Git-branch-specific binding or override for either variable.
We have also ruled out an application authentication defect:
-
the freshly pulled Preview pair passes the exact local
basicAuthOkimplementation; -
Base64 and UTF-8 round-trip exactly;
-
the deployed runtime confirms both environment variables are configured;
-
the incoming Authorization header is well-formed Basic auth;
-
wrong and missing credentials correctly remain unauthorized;
-
a clean redeployment of the exact source still receives the unexpected 6/16-byte pair;
-
no authentication logic was weakened.
The live deployment consequently returns 401 TASK_WALL_CALLER_UNAUTHORIZED for the credentials currently returned by the Preview environment configuration.
Could you please inspect the internal environment-variable resolution/snapshot for deployment:
dpl_DEqXN4qggKYMA97DFBTZqmev3NqT
and compare it with the current Preview environment bindings for project:
prj_nScKmZiuIpadgtWyDNaDxKy6D0hz
In particular, could you check for:
-
stale or shadow environment-variable bindings;
-
an obsolete environment-variable version/snapshot attached to the deployment;
-
unexpected custom-environment or branch resolution;
-
integration-created or internal variable bindings not visible in the normal project inventory;
-
deployment-context resolution related to this deployment being created through the CLI.
Please do not rotate or replace the current Preview values as part of initial troubleshooting. The configured values are internally consistent and recoverable; we want to identify why a new Preview deployment is receiving different values.
No secret values are included in this report; the fingerprints above are intentionally non-reversible.
Thank you.