Update — August 27, 2026 We completed one fresh diagnostic pass this morning.
Required environment variables are correctly scoped to Production and Preview. Fresh Preview deployment completed successfully. Preview deployment ID: dpl_2Werb6FjbULUZMDBDMofxDjvQhEL A single Join the Email List submission test returned HTTP 500. The request reached /api/contact and invoked the server-side function. Failure occurred during storage initialization. The Preview runtime treated CONTACT_BLOB_READ_WRITE_TOKEN as unavailable/falsy even though the variable is correctly configured in the Vercel dashboard. No outgoing Blob or email-service requests were made. Sanitized runtime evidence:
POST /api/contact → HTTP 500 Timestamp: 2026-08-27 09:06:41 CDT Function duration: 221ms Request ID: sq5db-1787839601363-884d9bccaee8
Sanitized error:
ENOENT: no such file or directory, mkdir '/var/task/data/contact'
The application fell back to local filesystem storage because the Preview runtime did not receive a usable contact Blob token.
No Production deployment occurred and the live website was not changed.
Could Vercel staff please investigate why this correctly scoped Preview environment variable is not being injected into the runtime?