{"section":"known-issues","requestedLocale":"en","requestedSlug":"secrets-take-hours-to-propagate-to-builds-in-webops-faststore-platform","locale":"en","slug":"secrets-take-hours-to-propagate-to-builds-in-webops-faststore-platform","path":"docs/en/known-issues/FastStore/secrets-take-hours-to-propagate-to-builds-in-webops-faststore-platform.md","branch":"main","content":"## Summary\n\nWebOps secret updates sometimes take hours to become available in FastStore builds, instead of the expected few minutes. The visible symptom is that new or edited secrets are missing from the build image/environment, even after triggering a new deployment.\n\n## Simulation\n\nPrerequisites: A FastStore project using WebOps with Variables and Secrets configured.\n\nSteps:\n\n1) In WebOps → Settings → Variables and Secrets for the target account/environment, create or update secrets. Record the save timestamp.\n\n2) Trigger a new deployment (either via commit or by starting a deployment in WebOps) and note the deployment link and build time.\n\n3) Inspect the resulting build image/environment variables. The issue reproduces when the newly saved secrets do not appear in the build for an extended period (potentially hours).\n\n## Workaround\n\nAfter saving secrets, wait a few minutes and then trigger a new deployment. If secrets are still missing, open a support ticket immediately with:\n\n- Account/environment, exact secret names (no values), secret save timestamp, deployment link, and build time."}