Skip to main content

​
Cannot create or save

Backend save validation checks shape and types. It does not execute the rule against an empty snapshot or prove the action can settle. Division by zero can still occur at runtime; guard the denominator first.

​
No intent appears

Check these in order:
  1. Lifecycle: is the intended strategy RUNNING, not just saved? Do not start an inactive exercise merely to investigate.
  2. Vault and target: check kill switch, pause, emergency locks, upkeep, and execution readiness. Do not clear an incident lock to force a test.
  3. Inputs and rule: inspect the current supported fields and their freshness. For the reserve example, idle exactly at the 10% trigger should not publish.
  4. Size: check the first hook’s units and positive integer amount. A sub-unit positive value truncates to zero.
  5. Publication gates: check conviction, cooldown, rate limits, and an occupied per-strategy concurrency slot.
Intent History records submitted intents, not every false rule evaluation. If no row exists, use the editor’s available state or authorized engine diagnostics; missing observations are not proof of a zero balance.

​
An intent failed or is still executing

Open the exact intent and inspect state, error, execution ID, and fills before considering another submission. The public deposit investigation includes a real pricing-timeout row and its empty fills response.

​
Simulation does not answer the question

Check selected saved IDs, model inputs, and whether a result was loaded from cache. Unsupported inputs are a coverage limit, not a reason to remove a live safety condition. Follow the run and review flow. For persistent failures, retain the exact ID/version, input context, error, and transaction evidence. Stop new risk-taking activity where appropriate and escalate. Archiving and cloning a failing strategy loses continuity and does not resolve the cause.