When your agent cannot act

An Execute agent sends you a message when it cannot act. Match the reason and next step in your notice to the sections below, not its exact words. Most notices are written from the run's facts, so the phrasing can vary. Token names and transaction ids are kept as recorded. Token amounts in the message—including amounts spent and remaining limits—are rounded to at most four significant figures. The linked transaction shows the exact amount that executed.

Every Telegram agent message has one button. When you can do the action yourself, Prepare it yourself takes priority. With no direct action, the button is Ask Signo when Chat is the next step, otherwise Open Agents. Deletion notices use Open Agents. Ask Signo opens Chat with the notice as a question and uses the docs to explain it; it does not sign a transaction or restart the agent. The message also says when the agent tries again. For details, see What you authorize with an Execute agent.

The lifetime limit is used up

The notice says the remaining lifetime limit cannot cover the firing, or the limit has been used up. The row can show Limit reached.

To raise the lifetime limit:

1. On the Agents page, click the agent's row.
2. In the Limits remaining card, press Change limits.
3. In Lifetime limit, enter an amount larger than Spent so far.
4. Press Sign the change and sign in your wallet. If your wallet asks for a token approval first, approve it.

The change keeps the same permission, and what it already spent still counts. The agent acts the next time your condition becomes true. If your condition is still true now, press Pause and then Start on its row, and it can act at the next check.

The token approval is too small

The notice says the token approval to the Shield is missing or too small for the firing plus its fee.

To approve the token again:

1. On the Agents page, click the agent's row.
2. In the Limits remaining card, press Change limits. You can keep the limits.
3. Press Sign the change. If your approval is smaller than what the permission can still spend, your wallet asks you to approve that amount first. Approve it, then sign the change.

All your permissions on the same token share one approval.

The balance is too low

The notice says the wallet's token balance is missing or too small for the firing plus its fee. The row can say You do not hold enough. This message has an Open Agents button, not Prepare it yourself.

Send more of the permission's token to the wallet that signed the permission. The wallet must hold the amount plus the 0.1% fee. A swap with a fixed amount needs the full per execution limit plus the fee, in balance and in approval. Native OKB does not count for a WOKB permission on X Layer; native ETH does not count for a WETH permission on Arbitrum. The agent tries again at the next check, within the hour.

Your Aave position leaves nothing to do

These messages come from agents that repay, sell collateral, withdraw or claim. Nothing was executed.

• Nothing to act on. The target health factor is already reached, there is no debt, collateral, vault share, reward or transferable balance, the amount rounds down to zero, or Aave has no collateral price. You do not need to do anything. The agent tries again at the next check, within the hour.
• No debt token in the wallet. The agent repays from your wallet. Send the token your debt is in to the wallet that signed the permission.
• The target cannot be reached by selling collateral. The target is part of the permission you signed, so Edit cannot change it while that permission is live. To use a different target, press Delete, complete Revoke and delete, then set up a new agent. Or repay on Aave yourself.
• The health factor is too close to 1 to move collateral. At a health factor of 1.01 or less, the agent cannot move your collateral. To raise your health factor now, repay part of the debt from your wallet or add collateral on Aave yourself.

The agent could not work out the amount

The notice says the agent could not determine an amount or a permitted route, or the route's price impact was too high. As a safety step, nothing was sent.

1. To act now, press Prepare it yourself on the message. You review the action in chat and sign it.
2. Or wait. The message says when the agent tries again.
3. To help the agent work out the amount, press Edit on the agent's row. Give the amount as part of your balance, for example "a quarter of my USD₮0". If the swap can buy several tokens, name one.

A venue changed and Signo has not reviewed it

The notice says a venue's on-chain code changed and Signo has not reviewed it yet. This is a safety stop, and nothing moved.

You do not need to do anything. The agent tries again after Signo reviews the change. To act now, press Prepare it yourself on the message, then review and sign.

A venue is a contract that the action calls, for example Aave or the OKX DEX router. Before each execution, Signo compares each venue with the code a person reviewed. If the code changed, Signo blocks executions through that venue until a person reviews the change.

The venues could not be checked

The notice says the agent could not verify a venue it routes through. Signo does not execute through a venue that it cannot check, so nothing was executed. You do not need to do anything. The agent tries again at the next check, within the hour.

Execution has stopped

The notice says execution has stopped and gives the reason; it need not use those exact words.

• Signo paused execution or its sending key. Your permission and your funds are untouched. You do not need to do anything.
• The permission expired or was revoked. Press Set up a new permission on the agent's row.
• The Shield has no record of the permission. Press Edit on the agent's row to set up a new permission.
• A lifetime limit, token approval, balance or amount problem: fix it as the sections above say. Then the agent waits for your condition to stop being true and then become true again. To re-arm it sooner, press Pause and then Start on its row.

The agent was deleted

You do not need to do anything. When you delete an Execute agent on the Agents page, the app revokes its permission first (Delete, then Revoke and delete), so nothing can execute under it. The notice confirms whether the permission was revoked or had already expired.

An app connected to your account, such as Claude, cannot delete an Execute agent while its permission is live; it asks you to use Revoke and delete. If it deletes one whose permission has ended, the message names the app.

The token approval stays. If no other agent uses it, you can remove it in Settings → Wallet permissions → Unallocated Shield token approvals.

Failed attempts: I will not retry

The notice gives the reason the last attempt failed. A confirmed reverted attempt moves nothing, and you pay no Shield fee for it. To see why it failed, open the History tab on the Agents page. If the cause is not clear, for example "the Shield refused it for a reason Signo could not read", press Report a problem on that attempt. It opens an email to support with the details filled in.

After the agent stops trying, it tries again when your condition stops being true and then becomes true again. To re-arm it sooner, press Pause and then Start on its row. It can then act at a later check while the condition is true.

Read the retry status in the notice:

• One retry is planned. An attempt failed and nothing moved. One retry comes within the hour.
• Both attempts failed. The retry failed too, so this run stops trying.
• The condition cleared. The condition stopped being true before the retry, so the failed transaction will not be retried.
• The last transaction is still unconfirmed. No second transaction is sent for this crossing. The first can still go through; do not treat it as a confirmed failure.
• The next attempt must wait. The signing service allows at most two execution attempts for one permission in a rolling hour. The notice gives the next available time.
• The firing limit was reached. A repay from collateral with Keep going until the target turned on used its 10 firings for one crossing, short of your target health factor.
• The run timed out. One crossing stays open for 6 hours at most.