States, actions, and reasons

This page covers the stable operator vocabulary currently visible in the product. Exact result messages may add context.

Run outcomes

Value	Meaning
completed	Complete observation and evaluation finished
skipped_peer_down	SVM peer health precondition failed
skipped_observe_incomplete	An ONTAP read, pagination sequence, or record count was incomplete
skipped_orphan_delta_guardrail	Too many relationships would enter orphan state in one run

Relationship states

Value	Meaning
initializing	Relationship exists but the baseline has not completed
managed	Steady state under DonkeyFleet creation intent or explicit automation ownership; observed healthy
drifted	Drift detected against intent (see reasons below)
orphaned	Expected source identity is absent and orphan grace has started
adopted	Existing relationship is monitored but remains mutation-excluded until profile binding
suspended	Relationship is outside supported active ONTAP states, is unhealthy, and is not an active initializing baseline; mutation is excluded

During a baseline, ONTAP reports the relationship as uninitialized and unhealthy for hours. That is ONTAP-reported health, distinct from the initializing lifecycle state, and it is not suspended.

As of 1.1.0 the controller does not yet transition relationships into or out of suspended; the state is defined but automatic suspension is planned.

Plan actions

Action	Meaning
protect	Create destination volume, relationship, and baseline
resize_dest	Increase destination size
set_tiering_policy	Change destination tiering
delete_orphan_destination	Delete approved destination relationship and volume

Fill growth also records destination_fill, autonomous_grow_applied, and autonomous_grow_failed episode outcomes.

Decisions and reasons

A plan item records a decision (such as awaiting_approval or approved) separately from the reason that produced it. The reasons currently emitted:

Reason	Operator response
destination_fill	Review logical usage, snapshots, and recommended growth
tiering_policy_mismatch	Verify selected target tiering
orphan_grace_elapsed	Independently verify deletion identity and retention
orphan_transition_guardrail	Investigate unexpected source visibility loss
source_replaced	The source name now resolves to a new UUID; confirm the replacement is intended. The relationship is marked drifted, excluded from remediation and orphan cleanup, and never auto-remediated

No-op decisions are intentionally not stored as plan items. source_replaced is emitted as a drift reason and raises a notification, but it produces no automatic plan action — the replacement is never auto-remediated.