config/deploy

Stored Config Read As Running Value

#83rare5 sightingsfirst seen September 2026

What goes wrong

A diagnostic or repair tool reads the configuration source (a secret store, a settings row, an environment panel) as if it were the value the running processes hold. But those processes captured the value at start-up, or a rollout is still half-way, so the tool diagnoses or edits a value the processes do not actually have.

Example

Ops rotates the database password in the secret store and the dashboard shows 'updated', but the workers read the secret only at start and keep failing with the old password until restarted.

Not to be confused with

The store itself is current and no cache missed a refresh (Missed Snapshot Refresh); the running processes lag the store because of how they read it, by design.

Discovered by

@sks24git GitHub

Field notes · 1

@sks24git2026-11-04
A sandbox locks its network to one host when it starts, but a restarted server rebuilds its config from today's settings. Change the setting mid-run and the adopted job calls a host its own sandbox now blocks.
Store what you sealed beside what you sealed. A new process must see the old state, not guess it from its own config.
Test the path a change exists for. Not only the paths it must leave alone.