Skip to main content

States, actions, and reasons

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

Run outcomes

ValueMeaning
completedComplete observation and evaluation finished
skipped_peer_downSVM peer health precondition failed
skipped_observe_incompleteAn ONTAP read, pagination sequence, or record count was incomplete
skipped_orphan_delta_guardrailToo many relationships would enter orphan state in one run

Relationship states

ValueMeaning
initializingRelationship exists but the baseline has not completed
managedSteady state under DonkeyFleet intent; observed healthy
driftedDrift detected against intent (see reasons below)
orphanedExpected source identity is absent and orphan grace has started
adoptedExisting relationship is monitored but excluded from normal mutation
suspendedRelationship 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.

Plan actions

ActionMeaning
protectCreate destination volume, relationship, and baseline
resize_destIncrease destination size
set_tiering_policyChange destination tiering
delete_orphan_destinationDelete 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:

ReasonOperator response
destination_fillReview logical usage, snapshots, and recommended growth
tiering_policy_mismatchVerify selected target tiering
orphan_grace_elapsedIndependently verify deletion identity and retention
orphan_transition_guardrailInvestigate unexpected source visibility loss

No-op decisions are intentionally not stored as plan items. (Automatic source_replaced detection is planned, not yet implemented, so it never appears as a reason.)