> ## Documentation Index > Fetch the complete documentation index at: https://docs.ansio.trade/llms.txt > Use this file to discover all available pages before exploring further. # Autopilot errors and pending tasks > Understand expired proposals, permissions, unsupported changes, scheduled-task errors, stale evidence and tasks still waiting for verification. Read the task state and latest result before sending the same request again. An answer, a proposal and a completed action are different records. ![ANSIO Autopilot task proposal with the affected account and requested setting change.](https://mintcdn.com/ansio/Tv7Q0RwZX2L68I0t/images/docs/autopilot-task.jpg?fit=max\&auto=format\&n=Tv7Q0RwZX2L68I0t\&q=85\&s=396756af97174c54bf65c45d85b71a3c) A task proposal in the ANSIO demo. Review the account and proposed change before confirmation. ## A reply arrived, but nothing changed A chat answer does not execute a trade or change a setting. A request to act needs a saved proposal and confirmation. **Observe** watches; **Assisted** asks for approval. Autonomous changes still need an active authorization and permitted fields. Open the task card and read its state. If there is no proposal, the reply is an explanation rather than an executed action. ## Proposal expired or already reviewed The proposal is no longer available for confirmation. It may have expired or already been confirmed or dismissed. Refresh the task first. If it has completed, read its result. If the change is still wanted and the proposal expired, request a fresh one based on the current account state. A direct Telegram **Yes, execute** confirmation has its own two-minute expiry. Do not assume every type of Autopilot authorization uses that same duration. ## Scheduled start has passed Messages include **Scheduled start has passed. Request a new proposal** and **Scheduled time passed while paused**. Choose a new future time and request a new proposal. Review the timezone shown on the card; an old confirmation does not move the schedule forward automatically. For new scheduled requests, the supported start must be within 90 days and include a timezone offset. ## The approved task window has ended The authorization's end time has passed. Resuming requires a new proposal. This prevents an earlier approval from allowing work indefinitely. For an interrupted one-time action, the response can explicitly require a fresh proposal before resuming. ## Autopilot cannot change a field The field is not supported for that strategy or is outside the permitted operation. Read the named field and the approved bounds. A request in chat cannot grant itself extra permission. **Order size exceeds the approved order limit** means the requested size exceeds the strategy's approved order cap. ## Continuous task rejected Continuous tasks need **2–2,880 steps**, at least **five minutes apart**, and a total mandate of no more than **30 days**. Only supported settings or reference targets can be applied gradually. Discrete settings, such as level counts, must be changed once. If the request is one adjustment at one time, ask for a one-time or scheduled task instead. ## Choose a running strategy and at least one change The requested configuration operation needs a running strategy and an actual setting change. Open the account to confirm the strategy and its state. **This strategy is already running** is a different response: a duplicate Start request is unnecessary. Neither message is a reason to restart without reviewing the account. ## Account access denied or Task access denied The selected account or task is outside the signed-in user's permitted scope. The owner can review the user's account assignment. Telegram permissions are separate from web access. Changing the wording of the request will not change that scope. ## Too many questions **Too many questions. Please try again in a minute** is a request-rate limit. Wait before asking again; repeated submissions do not help. For **Enter a question of up to 2,000 characters**, shorten the request to the account, intended change and relevant limits. ## Older snapshot or missing evidence Autopilot treats snapshots older than two minutes as stale. Missing balances or positions are unknown, not zero. Use the response's account name and timestamp to see what was actually reviewed. If the answer cannot establish a cause, restore current account data before relying on a new action proposal. ## A change is already being verified The execution is being checked. Read the task again for its result before cancelling or creating a duplicate. For **Task changed. Refresh before reviewing**, reload the latest task state and review that version. ## Paused, Off or Authorisation expired These states can explain why autonomous work is not proceeding. Read the active account authorization, its mode, expiry and permitted fields. Resuming a task and renewing an account authorization are separate actions. Neither should be inferred from clearing the visible queue. ## Reference changed since the proposal A reference or binding changed after a Peg proposal was prepared. The old proposal no longer describes the current setup. Request a fresh review. **Peg proposal expired** means its two-minute validity ended; **Peg cooldown is active** means the one-minute interval since the last application has not elapsed. A move that exceeds its permitted step or total offset is rejected separately. ## Autopilot cannot hold the contract This alert means Autopilot recorded a problem it could not resolve within the permitted settings. Read the escalation, current depth or spread and the account limits. It does not silently expand its authority. Use [records](https://docs.ansio.trade/autopilot/records.md) to see the proposal, approval and result. [Modes and permissions](https://docs.ansio.trade/autopilot/modes.md) · [Questions and tasks](https://docs.ansio.trade/autopilot/tasks.md) · [Alerts](https://docs.ansio.trade/alerts/overview.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.