# Fix a problem (/users/guides/fix-a-problem)



Zerochord writes out the reason for every block and every failure. This page groups those
messages and says what each one asks of you.

## Before you can sign [#before-you-can-sign]

The signing button lists every reason it is disabled. Each one has a fix.

<Accordions>
  <Accordion title="No quote yet, so there is no minimum output to enforce on chain">
    Fill in the pair and the amount and wait for the quote panel to appear. Signing unlocks
    once a quote with a minimum output exists, so you always see the numbers before the wallet
    opens.
  </Accordion>

  <Accordion title="No wallet is connected">
    Connect a wallet in the Wallet panel. See [Connect a
    wallet](/users/guides/connect-a-wallet).
  </Accordion>

  <Accordion title="The wallet is on network id N and this deployment is something else">
    Your wallet is pointed at a different Cardano network from the one this deployment reads.
    Switch the network inside your wallet extension. The block clears on its own once the
    wallet reports the matching network.
  </Accordion>

  <Accordion title="The wallet holds no collateral">
    Every Zerochord route spends a Plutus script, and a script transaction cannot be witnessed
    without collateral. Set collateral aside inside your wallet, then return to the swap
    screen.
  </Accordion>

  <Accordion title="This wallet exposes no getCollateral method">
    The connected extension does not offer collateral through CIP-30. Connect a wallet that
    does.
  </Accordion>

  <Accordion title="This is a hardware wallet extension, and this route spends a Plutus script">
    Tick the checkbox above the signing button to accept that the device can refuse the
    signature. Ledger and Trezor both have a Plutus signing mode, and whether yours signs
    depends on the app version installed on the device. CIP-30 does not report that version, so
    Zerochord asks you rather than blocking or staying silent.
  </Accordion>
</Accordions>

## While quoting [#while-quoting]

**The venues on this network could not be read.** The chain could not be reached when the
app started, so there is nothing to quote from. Press **Try again**.

**The chain could not be read through the provider.** The quote request itself failed to
reach the chain. The message names the provider and the endpoint. Press **Try again**.
Zerochord shows nothing rather than an old or an assumed number, and it builds no
transaction until a quote reads the chain again.

**No quote.** The chain was read and no route came back for this pair at this size. Try a
different amount, or a different pair.

**Some venues could not be read.** Any quote below is routed over the venues that answered,
and its saving is measured against a baseline drawn from those venues only. An amber note
above the comparison says the comparison is incomplete and names the venues.

**Venues not being quoted.** This is a fact, not a failure. It lists venues that are not
part of routing on this network, with the reason for each.

## While entering the amount [#while-entering-the-amount]

**This amount does not fit in the asset's decimals.** You typed more decimal places than the
asset holds. Zerochord refuses rather than rounding, because rounding your input without
saying so would change the amount you are about to sign for.

**The two assets are the same.** Pick a different asset on one side.

**The slippage allowance must be a whole number of basis points under 10 000.** Enter a whole
number from 0 to 9999. See [Set your slippage](/users/guides/set-slippage).

## When you press sign [#when-you-press-sign]

**This transaction stopped being submittable, and nothing was sent.** The venue caps how long
a signed swap stays valid, and the window closed while the wallet dialog was open. Nothing
was sent and nothing was spent. Zerochord fetches a fresh quote for you automatically. Sign
the new one, and approve it promptly in your wallet.

**The pool is not in the state this quote was computed from.** The pool moved between quoting
and building, so the transaction would no longer match the quote. Requote and sign again.

**This route spans several venues, and each venue's builder emits its own transaction.** The
route you were quoted is spread across venues that need the settlement validator to be
combined into one submission. Try a different size, or use the direct route button if the
panel offers one.

**This route runs on another venue.** This deployment submits swaps on the venues it has
builders for, and the quoted route uses a different one. Try a different size, or the direct
route.

## After signing [#after-signing]

**Your order does not fill.** Routes that place an order are filled by a batcher afterwards.
The rate is bound by the minimum in the order and the timing is guaranteed by nobody. Watch
it under [Pending orders](/users/guides/track-a-pending-order), and [cancel
it](/users/guides/cancel-an-order) whenever you want the funds back.

**This browser has no record of that order.** Order tracking lives in this browser's local
storage. The order is still on chain. Open the app in the browser you placed it from, or
look the transaction hash up on a chain explorer.

**The stored orders could not be read.** The local record could not be parsed, so some orders
are missing from the list. Nothing on chain is affected, and your funds are still governed by
the orders themselves.

**A cancel says the order is already filled, expired or cancelled.** No unspent output of that
transaction is at the order address any more. If it filled, open the receipt to see what
arrived.

## Related [#related]

<Cards>
  <Card title="Connect a wallet" href="/users/guides/connect-a-wallet" />

  <Card title="Read your quote" href="/users/guides/read-your-quote" />

  <Card title="Cancel an order" href="/users/guides/cancel-an-order" />
</Cards>