Why won't my offer send? Limits and common messages

If an offer will not send, or a bulk batch stops partway through, this article explains the plain-English messages you might see and what each one actually means, so you know whether to wait, reconnect eBay, or simply skip that listing.

Where these messages show up

DashVue never shows raw error codes. There are two places a message can appear, and they are deliberately different.

When you use Quick send to send the same offer to every eligible listing at once, the result is a single aggregate line in the Quick send bar, not a list. Depending on how the run went it reads “Sent 26 offers”, “Sent 26 · failed 4”, or, if you hit eBay’s cap partway through, “Sent 26, then hit eBay’s hourly offer limit” with how many attempts are left and roughly how long to wait. It tells you how many went through, not which specific listings did not.

The reason a particular offer did not send shows in a different place: as a short red line directly beneath that listing’s own send controls. You will see it on the individual card on the Send Offers page, and on the same row in the “Ready to send” list on the Offers overview. That is where you read why one specific offer failed, one plain-English message per card.

“Hourly limit reached”

DashVue caps outgoing offers at 30 per hour on your account. This is a safety limit to keep your sending activity well within what eBay allows, and it applies across all your listings combined, not per listing. If a Quick send run reaches it, the batch stops at the cap: the summary tells you how many sent before the limit was hit, and the rest are simply not sent. There is no per-listing list to work through.

There is nothing to fix here. The limit resets on a rolling hourly basis, so the simplest approach is to wait and send the rest of your batch a little later. Splitting a large batch across a couple of hours also avoids running into the cap at all.

eBay’s own hourly limit

Separately from DashVue’s own cap, eBay enforces its own hourly limit on offer sending. If eBay itself declines a send because you have hit its limit, DashVue surfaces this as a plain-English hourly limit message rather than showing eBay’s technical response. In a Quick send run this is the amber summary line shown above, with how many attempts remain and roughly how many minutes to wait. The fix is the same as before: wait for the hour to roll over and try again.

“Not currently eligible”

This message means eBay does not currently consider that listing open for an offer. Eligibility is set by eBay based on buyer activity such as watching the listing or adding it to a basket, and it can change between syncs. If a listing was eligible when you started a bulk send but a buyer’s interest has since lapsed, or eBay simply no longer lists it as eligible, the send will fail with this message rather than going through anyway. It appears as the red line on that listing’s own card.

Skip it and check back later. Eligibility refreshes on your next sync, so a listing that is not eligible right now may become eligible again once a buyer shows fresh interest.

“Full Access needed”

Sending an offer writes a change back to eBay, so it needs a Full Access eBay connection. If your account is connected as read-only, the in-app send controls are replaced by a “Send Offer on eBay” link instead, so you can still view and draft but the send itself happens on eBay. Where a send is attempted without Full Access, DashVue tells you that Full Access is needed. Reconnecting your eBay account with Full Access permissions resolves this.

eBay rejects the offer

Occasionally eBay declines an offer for reasons on its side, for example a listing or buyer state that has changed since your last sync. When this happens, DashVue shows a plain-English rejection message on that card rather than eBay’s raw response. There is no DashVue-side fix for a rejection: it reflects a decision eBay made at the time of sending, so the best step is to re-check the listing and buyer on a later sync before trying again.