Validation and raw calldata
Validation checks whether txcast can safely render and coordinate the definition. It does not prove the future transaction’s business intent or guarantee that chain state will stay unchanged.
Common validation errors
Section titled “Common validation errors”- an execution account or chain is missing;
- a dependency references a missing node or creates a cycle;
- a variable key is missing, incompatible, or cyclic;
- an ABI function no longer exists or its argument cannot be encoded;
- native value is supplied to a nonpayable function;
- a condition has an unsupported return type; or
- a transaction batch is empty.
Follow the issue path shown by txcast, correct the draft, then validate again.
Use raw calldata
Section titled “Use raw calldata”Raw calldata is an escape hatch for a static call that cannot be represented by a saved ABI.
- Confirm the chain, target, selector, encoded arguments, and native value independently.
- Enter the complete hexadecimal calldata.
- Add a note explaining its purpose and why an ABI-backed call is unavailable.
- Review any warning that a saved ABI appears to expose an equivalent call.
Recovery
Section titled “Recovery”If a published run renders the wrong calldata, do not attempt to edit it. Cancel the run, correct and save the workflow, and stage a new run.