Skip to content

Diagnose Model Errors

Diagnose the earliest failing boundary that exists in your workflow. Most users work directly in XML and therefore start at the XML model boundary. Later runtime symptoms are often consequences, not root causes.

  1. Agent draft (DM JSON, Agent Authoring only): Fix typed node and property errors before compilation. DM JSON is a temporary Agent representation; see XML and DM JSON.
  2. Authoring guidance (Agent Authoring only): Resolve diagnostics such as missing bounds, unsupported sources, invalid relationships, or requested side effects.
  3. XML model: Fix XML syntax, element attributes, allowed child elements, and cross-field combinations linked by Contract IDs.
  4. Model loading: Resolve include, path, and configuration-merge failures.
  5. Runtime: Investigate data-dependent assertions, service connectivity, broker acknowledgements, and external side effects only after the static boundaries pass.

Every catalogued issue has a cause and resolution in the error-code reference. Element pages link the applicable rules and show both allowed and rejected combinations. Agent Authoring uses the same Issue and Contract IDs as the documentation.

When reporting a defect, include the smallest complete XML descriptor, the issue code, the failing Contract ID, and whether the proof stopped at XML validation, model loading, local runtime, or external runtime. Include DM JSON only when the failure occurred in Agent Authoring before XML compilation.