Has anyone else run into this? In Publishing → Adjust settings → Production app secrets, I add a new secret and save it — it appears to save — but after a refresh or reopening the list, the new secret is gone. This has happened twice. Workspace/editor secrets persist fine; it’s only the Production (deployment) secrets list that loses the entry, and the published app therefore never sees the new value.
I already have a support ticket open. Posting here to ask: is this a known issue, and is there a workaround — for example, another supported way to set a deployment secret so it sticks?
while support looks at it, logging just whether the key exists at startup (never the value) after a fresh republish would tell you if it’s only the settings list that’s lying or the deployment really never gets it
Thanks for the suggestion — we actually built exactly that check. The app logs which secret source the live process selected (never the value), and after the last republish a live delivery showed the process fell back to the legacy secret — the new key never made it into the deployment’s environment at all. So it’s the second case: the deployment really never gets it, not just the settings list lying. Still waiting on support to look at why it won’t persist.