Saved is not active: Test pins the acknowledged revision
Saving a profile in Nest does not call a model and does not prove a Soot is active. When Test is blocked, and which revision Test pins.
You edit a Soot's description, press save and see a success message. It is easy to assume the Soot now runs the new version. According to Soot's operation docs, not necessarily. Saved and running are two different things.
This post is for operators and developers who have opened Nest and want to know when a Test result is really about the version they just edited.
Saving a profile does not call a model
According to the operation docs, saving a profile does not call a model and does not prove the Soot is active. The saved version is what you want; the active version is what the Soot is actually using. The two are not assumed to be the same.
When Test is blocked
According to the docs, Test is blocked in two cases:
- the saved version differs from the active version;
- activation is pending (not finished).
If Test is blocked, that is not an error to work around. It tells you that the version you want to try is not the one that is running.
Test pins the acknowledged revision
When Test can run, it creates a conversation and pins the acknowledged revision. The result is therefore about exactly that revision, not about the version you are still editing.
The practical consequence: if you keep editing after a Test, the new edit is not in the old result. To find out whether it is better, wait until it is acknowledged, then Test again.
Nest has four areas
According to the docs, Nest has four areas: Overview, Conversations, Soots and Data Pool. A screen that looks fine does not replace checking the saved version, the active version and Test.
Next step
Open the operation docs and read the Test section next to your Nest screen. If you do not have Nest yet, get it from the download page. If you are just starting, One Soot, one clear job is the post to read first (Vietnamese).