What happens when a version is wrong?
The operator points the stable address back at an earlier published version. Nothing is rebuilt, the applications keep calling the same place, and the change is on the record.
· 3 min read
IN SHORT
The operator points the agent's stable address back at an earlier published version, or turns the address off while the question is looked at. The wrong version stays on the appliance but is no longer live. Every run it made is on the record, and because the step that acts always waited for a reviewer, a wrong draft did not become an action unless a person approved it.
It depends on how wrong, but the first move is the same in every case: the operator points the stable address back at an earlier published version, or turns the address off. Either takes effect for the next packet. Nothing has to be rebuilt, because the earlier version is still on the appliance exactly as it was published, and the desk's applications keep calling the same address.
Versions were designed with this moment in mind. One live version at a time means there is always a clear answer to which version is live and a clear act that changes it.
The first few minutes
A reviewer notices that drafts from the new version are wrong: citing the superseded policy, categorizing packets badly, proposing entries that make no sense. They stop those runs, which is their job, and tell the operator.
The operator has two choices. Point the address back at the earlier version, so new packets are handled the way they were before. Or turn the address off, so no new runs start while the question is looked at. Both are recorded with the operator's name and the moment. Neither requires a developer, a deployment, or a window.
What the wrong version did
Every run the wrong version made is on the record. The operator and developer can open those runs and see the packet, the passages read, the draft, and the reviewer's decision. That is usually enough to see what went wrong: a document set added to the bounds that should not have been, a step that reads the wrong field, a model choice that drafts differently than expected.
The reassuring part is what the record does not show. Because the step that sends, spends, or changes a record waits for a reviewer in every version, a wrong draft became an action only if a named person approved it. The runs the reviewer stopped made no call. The runs they approved are on the record with their name, and the desk can follow up on those specifically rather than on everything the version touched.
Fixing forward
The wrong version is not edited; versions cannot be. The operator or developer changes the design in Agency Studio or in the file, publishes a new version, and points the address at it. The wrong version stays on the appliance as a published version that is no longer live, available to open beside its run records.
If the new version is also wrong, the address goes back again. The site is never without a version it trusts, because the trusted one never went anywhere.
What the record shows afterward
The version history on the appliance tells the story in order: this version was published by this operator, the address was pointed at it at this moment, pointed back at this moment, and pointed at the corrected version later. The run records between those points name the version that produced them. An auditor reading it sees a wrong version, a prompt rollback, and the decisions people made in between.
For the mechanics of the pointing itself, see /resources/pointing-the-address-back-at-an-earlier-version.
Questions this raises
- Does rolling back lose any runs?
- No. Every run the wrong version made is on the record on the appliance, with its inputs, draft, decision, and any call. Rolling back changes which version answers new packets; it does not touch what already happened.
- Can a wrong version have taken an action nobody approved?
- No. The step that sends, spends, or changes a record waits for a reviewer in every version. A wrong version can produce wrong drafts, but each one that became an action was approved by a named person, and the record shows who.
- Is the wrong version deleted?
- It stays on the appliance as a published version that is no longer live. That lets the operator and developer open it beside the record of its runs and see exactly what it did, which is usually how the next version gets fixed.
KEEP READING