Manual: RAV3-1295
f629bd4fa13dfd84
- exception
- manual:RAV3-1295
- in-app frame
- none
- message shape
- none
- owner
- unmapped — no ownership glob matched
- events · users
- 0 · 0
- seen
- →
- environments
- —
- ticket · pr
- RAV3-1295 · Rapid-Assurance/V3#4183
Agent stages
fix
done 01M1NG9395A8check
done 01M1NG9395A8
Two of §5's five stages are drawn, because two are all anything writes.
plan is build-order step 5; provision and screen
need the sandbox, which is step 8. They are absent rather than grey — a cell reading
not reached about a stage that has never existed says the run stopped, which is
not what happened.
Four states, never three: skipped by policy means the pipeline decided not to,
not reached means it never got there. A stage with no agent_stages
row is the second, never the first. Each cell shows the most recent run
to record that stage — a cluster worked on many times shows where it stands now, not
where it started.
Decision history
-
CANDIDATE policy v4 · manual
-
CANDIDATE policy v4 · manual
Signals
No
observations rows — this is a manual cluster, derived from a request
rather than from error signal.