> For the complete documentation index, see [llms.txt](https://help.refractbot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.refractbot.com/modules/walmart/walmart-wednesday-drop-guide.md).

# Walmart Wednesday Drop Guide

Walmart releases their card products on Wednesdays, at 9:00 PM EST usually. This guide covers how to set up, what to expect from the queue, and how to handle the errors you're most likely to see during a drop.

{% hint style="info" %}
For step-by-step task creation, see the main [Refract Walmart guide](https://help.refractbot.com/modules/walmart).
{% endhint %}

## Task Creation & Multi-SKU Limitations

{% hint style="warning" %}
**Multi-SKU does not work with Walmart's queue system,** and never will.
{% endhint %}

* If you're targeting multiple products, create separate task groups for each SKU.
* You can reuse the same accounts and proxies across groups for different products.

{% hint style="info" %}
**How many SKUs per account?** We wouldn't recommend running the same accounts on more than 2-3 SKUs max. It's your bot and your accounts, so run it how you want. This is just our recommendation not to push past that.
{% endhint %}

## Setup & Drop Strategy

{% hint style="warning" %}
**Walmart+ should not be required for most drops,** unless we say otherwise. If it does turn out to be required and you don't have it, you may see "unknown response \[400]." Note that free trials and $1 trials do not work.
{% endhint %}

You do not need to pull fresh saved sessions every week if your previous sessions are still working. There's no data showing old vs. new sessions perform differently, so redoing them weekly shouldn't be necessary.

{% stepper %}
{% step %}

### Test your saved sessions early

Run a couple of tasks with Use Saved Session ON ahead of time.
{% endstep %}

{% step %}

### Check that they reach "Waiting for Restock" or "Waiting for Product"

If your saved-session task reaches "Waiting for Restock" or "Waiting for Product," you're good to go. Turn Use Saved Session ON for all tasks.
{% endstep %}

{% step %}

### Only regenerate if needed

Generate a new session only if your saved-session task fails to return to "Waiting for Restock" or "Waiting for Product." To regenerate, run your tasks with Use Saved Session OFF and let them fully log in.
{% endstep %}
{% endstepper %}

## Use Saved Session

This feature lets the bot reuse a previously saved login session instead of logging in again. Walmart has strict security at login right before and during drops, so skipping login makes tasks run faster and more reliably.

{% stepper %}
{% step %}

### Confirm tasks are logged in

Check the Accounts tab to verify your tasks are logged in.
{% endstep %}

{% step %}

### Turn on Use Saved Session

Enable Use Saved Session, then start your tasks 30-60 minutes before the drop. This gives the bot plenty of time to refresh the session and avoid login errors.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**Start your tasks 30-60 minutes before the drop.** Don't wait until the last minute. The early start is what lets sessions refresh cleanly and avoid really high PX before the drop.
{% endhint %}

{% hint style="info" %}
**"Setting cookies" every \~10 minutes is normal.** While tasks wait, they refresh the session roughly every 10 minutes, and you'll see a brief "setting cookies" status. This uses a small amount of proxy data, which is expected.
{% endhint %}

{% hint style="danger" %}
**Always enable Use Saved Session.** If you don't, the bot will try to log in from scratch, which may trigger PX blocks and leave you unable to log in.
{% endhint %}

{% hint style="warning" %}
If you hit PX blocks, let it retry. If it keeps looping on "setting cookies," toggle Saved Session OFF, restart tasks, and retry.
{% endhint %}

**Note on proxies:**

* If you're already logged in, the task begins using the proxy you logged in with.
* If that proxy gets blocked, the task automatically rotates to a new proxy in whichever proxy list is assigned to that task.

## Skip Monitoring & OID

{% hint style="danger" %}
**Never use Skip Monitoring for queue drops, ever.** Most Walmart Wednesday drops are queue drops, so Skip Monitoring should stay OFF. Enabling it on a queue drop will hurt you, not help.
{% endhint %}

{% hint style="info" %}
**OID (Offer ID) is optional and not needed** for queue drops. You don't have to find or enter it. Leave it blank unless we explicitly tell you otherwise in #dev-announcements.
{% endhint %}

Skip Monitoring exists only for non-queue drops, where speed is critical and you want to spam Add to Cart the moment the product goes live. It is not a queue-drop tool.

<details>

<summary>Using Skip Monitoring on a non-queue drop (advanced)</summary>

If, and only if, you're running a non-queue drop and choose to use Skip Monitoring:

* Add the PID (SKU) to the monitor section in advance of the drop.
* Add the OID (Offer ID) as well. It acts as a fallback if your monitor is blocked.
* At drop time, enable Skip Monitoring to force Add to Cart attempts using the PID and OID.

Both PID and OID are required here. Skip Monitoring will not function if only one is provided. Again, this does not apply to Walmart Wednesday queue drops.

</details>

## Monitor Delay (at drop time)

Your monitor delay controls how often the bot checks for the product. A lower delay means it picks up the product faster and gets you into queue sooner.

{% hint style="warning" %}
**About 30 seconds before the drop, lower your monitor delay to around `1000` (1 second).** This helps the bot pick up the product and get into queue as fast as possible the moment it goes live.
{% endhint %}

Don't run a super-low delay far ahead of time. Drop it down to around `1000` only in the final \~30 seconds before the drop, then let it run.

## Queue Behavior

Queue behavior during Walmart drops can be unpredictable. A few important things to understand:

* **Placeholder timers:** Queue timers like `29:59` or `9:59` are not your actual queue times. They're placeholders Walmart uses while it determines when (or if) you'll be moved forward.
* **Stuck in queue? Not broken:** Tasks stuck at placeholder times aren't broken. Walmart just hasn't issued a new queue time yet.
* **Waves release:** Walmart releases users in waves. Sitting in queue doesn't mean you won't get through. Do not end tasks early.
* **No monitor updates? Normal:** It's completely normal for the monitor section to look inactive while your tasks are in queue.
* **Try restarting some tasks:** Some users have forced a queue time by restarting tasks stuck at placeholder times. If you can afford to lose the task, try restarting a few.

**What specific queue statuses mean:**

* **Queue stuck \~30m:** Usually means you got in late and are effectively waiting at the back of the line.
* **Queue looping \~14m59s:** Can happen when Walmart is letting very few people through at a time. There's no known fix other than letting tasks run. It may be due to overlapping or flagged proxies or flagged accounts, but only Walmart knows for sure.

## Queue Proxies

{% hint style="info" %}
**Bottom line:** Optional, not required. If you do run them, use ISP proxies only. Don't use residential (resi) proxies as your queue list, as it defeats the purpose.
{% endhint %}

**How it works:** Queue proxies are only used to enter and wait in queue. Once you're through, the bot switches to your task proxy for the rest of checkout. If you don't set a queue proxy list at all, your task proxy is used to enter the queue by default.

{% hint style="info" %}
Some weeks queue proxies pass better, some weeks they don't, so diversify your setup. The goal is to optimize to get into queue as fast as possible.
{% endhint %}

## Common Errors & Fixes

Find your error below. Every error is listed in the "On this page" outline on the right, so you can jump straight to the one you're seeing.

### Access Denied (456)

**What it means:** The session is receiving 456 blocks (previously known as "Generating Session" loops).

**What causes it:**

* **Bot detection flow:** Temporary issues in how the bot mimics human behavior may trigger this. It's mostly resolved, but Walmart may still update its security unpredictably.
* **Accounts:** Flagged accounts may contribute. Re-logging into your account can sometimes refresh the session; otherwise, let the account rest.
* **Proxy (most common cause):**
  * The bot auto-rotates proxies after a 456 block.
  * Proxy location matters. Proxies just outside the U.S. (for example Mexico or Canada) have triggered 456 blocks, while U.S.-based proxies passed.
  * Low-trust proxies get blocked more often.

**How to fix it:**

* Let the task auto-rotate proxies and retry.
* Use U.S.-based residential proxies with a good trust score. Avoid international or mixed-location proxy pools.
* Try re-logging into the Walmart account to refresh session data.
* If you're already through queue and stuck here, removing the proxy and switching to your local IP can help push tasks through.

### Unknown Response \[400]

Often means Walmart+ is being required on a product but isn't on your account. See [Setup & Drop Strategy](#setup-and-drop-strategy). Free trials and $1 trials do not work.

### Unknown Response \[500] on Queue

A 500 means a site error on Walmart's end. There's nothing we can do if their site crashes. Let tasks keep running.

### Rate Limited on Queue

Walmart's site is crashing or erroring. The task retries when the site errors out and sometimes gets blocked in the process. This is the same situation as a 500. It's on Walmart's side, not yours.

### Unknown response when submitting login code

If you get an unknown response while submitting your login or verification code, check #dev-announcements in Discord for the latest guidance on it.

### Proxy Error

Your proxy is dead, banned, out of bandwidth, or the provider is offline.

### Connection Error

Typically due to proxy or internet issues. Your bot couldn't reach Walmart.

### Invalid Address Details

Walmart has rejected your shipping address.

* Enter it manually on the Walmart site to test it.
* Use their suggested format (the bot will do this too if available) or adjust your jig if blocked.
* If you see "Invalid Address Details" in the bot, it means Walmart did not give an override option or a suggested address.

### Invalid Card Details

This is an authorization charge being declined at the bank or issuer level, and there is nothing staff can do for it. The fixes below are all on your end.

**Why you may be seeing this:**

* Even if your cards work fine on other sites, Walmart may reject them if you reuse the same card across multiple profiles or tasks.
* Each task sends an "invisible" $0.00 authorization charge to your bank when adding the card.
* Too many authorization attempts in a short time can cause your bank to temporarily block the card on Walmart.

**How authorization charges work:**

* When you add a card to an account, Walmart sends an authorization charge.
* Running many tasks at once creates multiple rapid charges.
* Most card providers treat this as suspicious and temporarily stop further authorizations. This is a fraud-prevention feature, not usually a permanent ban.
* Generating new cards from the same provider does not get around this. The blocks are enforced at the custodial (bank or issuer) level, not the individual card level.
* American Express (AMEX) is the worst with this. Some people can now only add a card to one account per day before getting blocked.

**How to fix it:**

* If your card details are correct, you likely just need to let the card cool off.
* The block usually clears on its own after some time, depending on your bank.
* Once cleared, you can start tasks again with that card.

**Tips to avoid it:**

* Add cards to your accounts extremely slowly. Spreading them out over time is the best way to avoid authorization blocks, and this matters most with AMEX (as little as one card per account per day).
* Limit to one task per card during setup to reduce authorization spam.
* Reuse the same card on the same Walmart account whenever possible.
* If a card is already saved on the account, Walmart won't resend the authorization charge.

## Troubleshooting any other error

{% hint style="info" %}
**This applies to all sites.** For any generic unknown error, task crash, or unknown response that isn't listed above, work through these steps before opening a ticket.
{% endhint %}

{% stepper %}
{% step %}

### Check your proxies

Make sure they have data and ping properly. This is the cause of 99% of "unknown errors," since different proxy providers sometimes return unique errors we don't handle.
{% endstep %}

{% step %}

### Check your profiles

Make sure no info is missing or incorrect, especially if you imported from somewhere else like AYCD. This is the cause of 99% of "unknown response" or task-crashed errors.
{% endstep %}

{% step %}

### Still failing? Open a ticket

If your profiles and proxies are good and you're still erroring, open a ticket. Unknown means unknown, so we'll have to check the logs.
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.refractbot.com/modules/walmart/walmart-wednesday-drop-guide.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.