Common errors

Common execution failures users may encounter in Terminal 1.

Most Terminal 1 failures fall into a small number of categories. In general, if a route cannot execute safely under current conditions, it will revert rather than partially complete.

• Missing or insufficient authorization: required approvals/permits are missing, expired, or below the needed amount (including Safe batch approval steps that were not executed).

• Insufficient balance or available funds: the selected funding source (wallet, ERC‑4626 vault, Aave, Morpho) cannot provide the required amount at execution time.

• Quote or liquidity changed: swap quotes became stale or liquidity moved between preview and execution, causing the route to fall outside its bounds.

• Fees or buffers not covered: fees or UI safety buffers increase required amounts and the route no longer satisfies downstream obligations.

• Venue-level revert: an external venue rejects the action (capacity, collateral constraints, paused markets, market parameters changed).

• Market incompatibility: the selected market/term/asset combination is not eligible for the workflow (e.g., rollover target market not compatible or not available).

• Execution timing issues: deadlines expire, block conditions change, or Safe signing latency causes the route to become stale.

When troubleshooting, start by confirming the position/market selection, then verify authorization scope, then re-run preview with current market conditions.

Protocol-linked failures

Some failures come from underlying product rules.

Examples include maturity timing, collateral requirements, or incompatibility with the destination position.

See Rollovers, Maturity, and Margin maintenance.

A failed route does not mean the quoted workflow is permanently unavailable.

It often means execution conditions changed before confirmation.