> ## Documentation Index > Fetch the complete documentation index at: https://docs.panofx.com/llms.txt > Use this file to discover all available pages before exploring further. # Why your node declined > Every decline reason the node sends, what it means, and what to do. A node that does not quote an RFQ answers with a decline and a reason. Declines count as replies for your [reliability score](/resolvers/operate/reliability), so a decline is always better than silence. The dashboard and your console show them by reason. | Reason | Meaning | What to do | | -------------------- | ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | | `wrong_chain` | The request names a chain your policy does not list, or your RPC answers for a different chain than the policy says | Check `chain_id` and `rpc_url` | | `unknown_executor` | The request names a settlement contract or program your policy does not | Upgrade the node, or set `PANOFX_EXECUTOR` | | `no_corridor` | Your policy has no corridor for this pair on this chain | Add the corridor, or nothing | | `bad_terms` | Solana only: the request's fee or fee-payer terms would have you pay, or are malformed | Nothing; this protects you | | `no_token_account` | Solana only: you have no token account to receive what the taker sells | `panofx-node approve --policy policy.yaml` | | `bad_amount` | The request's amount could not be parsed | Nothing | | `below_floor` | The price would be under your spread floor | Nothing; this protects you | | `ticket_cap` | The request is larger than `max_ticket_base` | Raise the cap if you want larger fills | | `daily_cap` | Today's volume reached `daily_cap_base` | Resets at 00:00 UTC | | `inventory_floor` | Filling would take a balance under `inventory_floor` | Add inventory | | `no_rate` | No fresh rate, or yours is too far from the band | Check your rate sources, or use `oracle: true` | | `paused` | You paused the node | `panofx-node resume` | | `signer_unavailable` | The signer errored or took longer than 700 ms | Check the keyfile passphrase or your MPC backend | | `below_minimum` | The request is under `min_ticket_base` | Nothing | | `clock_skew` | Your clock and the chain disagree by more than `max_clock_skew_seconds` | Enable NTP | | `rpc_unavailable` | The RPC failed | Add `rpc_fallback_urls` or change provider | Declines that are all `no_rate` in the first seconds after connecting are normal: the band arrives within 10 seconds of the hello. If they continue, your `rate` block is the place to look. A node whose chain is degraded (RPC down, clock off, signer failing) reports that state in its heartbeat and is not sent RFQs on that chain until it recovers. Its other chains keep quoting.