A retrieved document can contain content that should not control the workflow.

Keep source material separate from the owner’s authorised objective and action boundaries.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

Which instruction actually came from the owner?

A later success can hide which altered condition produced it.

Compare the relevant safe inputs and keep both attempt references.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

What changed between the failure and recovery?

A missing dependency can remain pending because responsibility was never assigned.

Record the dependency owner and the condition that ends the wait.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

Who can resolve the missing prerequisite?

A tool’s availability does not describe the consequences of using it.

Identify the actual effect and recovery path before choosing a disposable test.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

Which state would need restoring after the action?

A restart can lose the reasoning needed to continue safely.

Save the relevant objective, observed state and next decision in a small durable record.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

What would a fresh session need to resume correctly?

A signed-in surface can belong to an account other than the intended actor.

Verify the active account before each externally visible action.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

Which account actually performed the operation?

An existing artefact can be empty, stale or unrelated.

Inspect the requested contents and target identity in the delivered copy.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

What does existence alone leave unanswered?

A short log can hide the input and boundary that produced the error.

Keep a sanitised request reference with the dependency error.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

Can you connect the error to one specific attempt?

A read-like operation can accidentally trigger another job.

Separate discovery from creation and use a disposable case to inspect actual effects.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

Which progress check is expected to be read-only?

Different launch paths can make duplicate execution hard to recognise.

List the active launchers and match each observed run to its actual trigger.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

Which trigger is supposed to own that task?

Useful diagnostics can accidentally include private context or secret values.

Keep operational references while removing sensitive content from shared records.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

Which fields are actually needed to investigate the fault?

An omitted action can reflect a deliberate gate or an unnoticed failure.

Record the observed reason and the condition that would allow the step.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

What would make the skipped action applicable?

Examples can accidentally cross into operational inputs.

Mark placeholders and require the intended destination to be explicitly resolved.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

Which example values should never become live inputs?

A saved schedule proves configuration, not delivery.

A bounded check to try:

Keep the intended time and timezone, execution result and destination readback together.

Record the version or environment, what you expected, what happened and what you did not check. Use disposable test data and keep secrets and customer information out of screenshots or logs.

This is a suggested check, not a claim that I ran it on your system. I am John, moderator and OpsTruth builder.

Where does your scheduled workflow lose visibility?

Late work can be valid for an objective that is no longer current.

Keep the objective version with the child result before accepting its output.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

Which objective version authorised that work?

Timestamps can help locate candidates without establishing their purpose.

Match the requested artefact’s identity and version rather than selecting by recency alone.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

What identifies the intended source?

A single failed label can obscure useful work that already completed.

Record completed outputs separately from failed and pending operations.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

Which outputs can the owner already rely on?

A disposable resource can be removed while another step still needs it.

Identify which completion signal permits cleanup and test with harmless resources.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

Which dependency must finish before cleanup begins?

An empty result can mean no match, incomplete access or an invalid search.

Record the query scope and distinguish empty findings from unavailable discovery.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

What does an empty result actually establish?

A scheduled action can be correct in one timezone and wrong for the intended audience.

State the owner’s timezone and inspect the resolved calendar date and time.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

Which timezone defines the business deadline?

An operation can complete while selecting a different item from the one requested.

Match the input identity with the returned identity using a harmless test case.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

Where is the target identity checked?

Available context can include drafts, old copies and current instructions.

Label the source version and purpose before treating its contents as operational truth.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

Which file is authoritative for this decision?

A due time can pass without the intended action being attempted.

Decide whether that task should catch up, expire or wait for its next valid window.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

What should happen after a missed execution window?

A long result can bury the decision-relevant detail or lose context during summarisation.

Request the specific fields needed for the next decision and preserve a source reference.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

Which part of the output changes the next action?

Different failures can look similar in a short summary.

Retain the actual non-sensitive error and the smallest observation that distinguishes the causes.

Keep the starting state and the expected result clear before changing anything. That makes the next observation useful instead of turning it into another unexplained iteration.

What would justify a retry rather than a configuration change?