Errors

Troubleshoot common errors and status codes in PanAIO.

Troubleshooting

Use this page to identify common errors quickly.

Most issues come from one of these areas:

• proxies

• product state

• invalid profile format

• site-side rate limits or downtime

If an error keeps happening after changing proxies, restarting tasks, and checking your setup, contact support.

How does bot handle errors?

The bot usually handles errors by switching proxies and retrying after a delay.

Status colors show what happens next:

• Yellow — The bot will retry automatically.

• Red — The task stops and will not retry automatically.

Red statuses usually mean the issue needs a manual fix. Common examples are invalid task data, or unsupported payment and profile details.

General errors

Proxy errors

• Proxy error 402 or Proxy error 407 — You finished your proxy data, or the proxies expired.

• Proxy error xxx — The issue is usually with the proxy itself, not the bot. Check with your provider.

Site and task errors

• 404 — Product not found. This usually means the product is not loaded yet, pulled, or out of stock. If you see it on a confirmed in-stock item, contact support.

• 403 — Proxy banned, either temporarily or permanently. It can also happen after antibot changes. Try another proxy type or region.

• 429 — Rate limited. Increase delays, restart later, or let the proxies rest.

• 500 / 501 / 502 / 503 / 504 — Site-side issue. The site is usually overloaded. Let the tasks retry.

• 400 — Bad request data. Common causes are unsupported country, invalid profile data, or bad task input.

• 401 — Expired session or logged-out account. Contact support and include logs if the issue keeps happening.

• 422 — Usually out of stock or a product state issue.

• Timed out errors — These can come from exhausted proxies, site downtime, unstable connections, or proxy bans.

What to try first

1. Restart the task.

2. Change proxies or proxy region.

3. Check product link, country, profile, and payment method.

If the issue persists after following the steps above:

1. Open Settings.

2. Click Start Recording.

3. Perform the action again.

4. Export the logs.

5. Send the logs in your support ticket.

About You

See the full About You guide.

• No carts after restock detected — Set a quantity.

• ATC error 400 — Set a quantity.

• ATC error 403 — Change proxies.

• 403 — Proxy banned.

• 429 or data error 429 — Proxy rate limited. This is usually temporary.

• 501 / 502 — Site issue or module issue. Wait for the site to recover, or wait for an update if needed.

• 400 — General task issue, usually not proxy-related.

• 406 — Payment method issue. Try a different method or fresh accounts.

• Error fetching product on monitor tasks — Change monitor proxies.

• Payment failed — Use fresh accounts.

• Dummy checkout — Run more accounts than tasks. It can still happen occasionally.

Asos

See the full Asos guide.

• Discount error — Use uppercase discount codes, for example ASOS instead of asos.

• Orders canceled — This is usually retailer-side. There is no direct bot-side fix.

Adidas

See the full Adidas guide.

• Refreshing session — Restart tasks first. If that does not help, change proxies or generate fresh accounts.

• Monitor 404 — Change monitor mode, or remove the product if it was pulled.

• No stores within 50km — Change the city to the closest supported store.

• Init error 403 — Change proxies.

• Retrying init — Clear session, change proxies, or generate fresh accounts.

Zalando

See the full Zalando guide.

• ATC error 403 — Change proxies.

• Dummy OOS — Stop and start the task again.

• Payment error — Restart the task. If it still fails, the selected payment method is likely missing on that account.

• Dummy checkout — Rare, but it can happen.

• Checkout failed on an in-stock product — Your proxies are likely banned at checkout. Wait a few hours or change proxies.

• 422 ATC error — Switch to exclusive mode.