Steam Trade Error? Check Before Sending Again

You sent a trade offer, an error appeared, the other person says nothing arrived, and the items are still in your inventory. Before clicking again, open your sent offers. An error on the screen is not proof that no offer was created.

Offer creation, confirmation, the other person's acceptance, and item delivery are different stages. You need to know which stage you reached before deciding whether to inspect the existing offer, create a new one, or contact Support. While the cause is unknown, I would not start changing account settings.

This article is based on Valve documentation checked on September 5, 2026. The situations used as examples are hypothetical; they are not measurements of Steam's error rate, recovery time, or the size of an outage.

Start with the action immediately before the error#

Write down where the process stopped: did the item-selection screen fail to open, did the error appear after Make Offer, or did it happen while accepting an incoming offer or confirming it on your phone? Record the error text exactly and include the time zone with the time. “Error after confirmation” is less useful than the button you actually pressed.

Steam's trading guidance explains that an offer can be created from an inventory's trade-offer page or a friend's profile, followed by mobile-app or email confirmation as applicable. Passing the creation screen does not mean the offer was sent. If the error disappears when you reopen the page, do not create a new offer just to reproduce it; inspect the records that already exist.

Offer lists and item history answer different questions#

Open Trade Offers in the inventory. If you sent the offer, look under Sent Offers; if you stopped while accepting one, look under Incoming Offers. If it is not in the current list, check the offer history. For an item movement that is already complete, compare the trade history. Steam's trading support keeps those paths separate.

Check the other account, when the offer was created, and the items on both sides so that an earlier, similar offer does not confuse the result. The table is for states visible on the current screen, not for explaining undocumented error numbers.

If the list failed to load, the result is not “no offer”; it is “not confirmed yet.” Distinguish that from a successfully loaded list in which the offer is absent. If the other person says it never arrived, ask whether they missed a notification, cannot find it in their list, or did not receive the item.

The Steamworks IEconService documentation also distinguishes sent and received offers in GetTradeOffers from completed trades in GetTradeHistory. You do not need to issue an API key to follow the checks in this article.

“Pending” does not say whose step is next#

The trade-offer FAQ says the required confirmation happens before an offer is sent, and that confirmation cannot be disabled. If your confirmation is still waiting, open that existing request instead of making another offer. Read the counterpart and both item lists against the intended trade.

If you completed your confirmation and are waiting for the other person's response, the offer has already been created. That is different from a sending error. It is also different from a trade that both people accepted but Steam is holding before delivery; see the difference between a trade hold and a Market hold.

CS2 does not simply use a generic hold period here. The Trade Protection guidance below describes a different protection system in place of the older trade-hold or escrow model. The word “pending” alone does not justify predicting that an offer will finish in minutes or days. Follow the current screen if it shows an end time or an action you must take.

An old offer can stop being valid even when the item name matches#

The trade-offer FAQ says the same item can be included in more than one offer, but once one offer is accepted, other pending offers containing that item become inactive. An item traded away or sold on the Market also makes the associated offer impossible to accept. Adding an item to an offer does not remove it from the inventory before acceptance.

For example, imagine sending the same card to A and B in two offers. After completing the trade with B, the old offer to A cannot use that card. Obtaining another card with the same name later does not make the old offer point to the replacement. An item currently in the inventory and the validity of an earlier offer are different questions.

Check the item promised by the other person in the same way. They may have sold or traded it even if your own item is still present. Confirm both items and the offer state before guessing at the reason. If you agree on a new item, that is a new offer; compare its item, attributes, and quantity again. Check the item's tradable date and restriction marker separately.

A valid item does not make every combination valid#

The Trade Protection guidance checked on September 5, 2026 names Counter-Strike 2 as the supported game. One trade can contain only items with the same protection level. A combination of a CS2 item and an item from a game that does not support the protection is not allowed. Each item being tradable does not mean that the combination is allowed.

Do not solve that restriction by splitting an agreed exchange into two one-sided trades, with one person sending first. That changes the consideration into a separate promise rather than the exchange you were reviewing.

During the 7-day protection period for a received CS2 item, consuming, modifying, or transferring it is restricted. This is not a timer for a server error to repair itself. Whether the item can be used in the game and whether it can be traded again are separate questions.

If the error names an account restriction, check Steam's restriction guidance and the exact message on your screen. Valve says a reason is often shown and that Support cannot change a restriction. Do not substitute another person's remaining wait for the date shown on your own account.

Turning off Steam Guard or removing the mobile authenticator is not a refresh. Deleting cookies or trying a new browser can also be related to a new-device restriction, subject to Steam's documented exceptions. These settings should not be changed blindly as the first response to an unknown trade error.

Retry or cancel only after checking the state#

Reopening a page to read it is not the same as creating a new offer. If an existing offer is valid, inspect that offer. Only after the lists, history, and trade record loaded normally, no offer was found, and the account and item conditions look correct should you consider trying again. Check the records after the next attempt as well.

Identify what changed from the first attempt: was a new item agreed, did the displayed restriction actually end, or did nothing change? If you do not know whether the old offer is still active, avoid creating a duplicate. If several offers already exist, compare their items and quantities and identify the intended offer. Do not tell the other person to accept “any one.”

Cancellation also depends on state. Canceling an offer waiting for a response is not the same action as canceling a trade that both sides accepted and Steam is holding. Valve's hold guidance says canceling the latter brings a protective trade restriction. Reversing a protected trade has its own scope and restrictions. Do not cancel or reverse everything just to see whether the page refreshes.

Do not use an unofficial table of error numbers as a diagnosis when the official documents do not establish that mapping. A tool's state value and a Steam error number are not automatically the same thing. Record the number and wording, then check whether they describe the state you actually observed.

Keep Steam and a third-party service's status separate#

Review Steam's records separately from an outside service's order or incoming/outgoing status. If Steam shows the item movement as complete while the website still says “processing,” the question belongs to that website. Sending the item again would add another movement; it would not repair the first record.

In a support message, distinguish the outside order number from the Steam offer address or identifier. “Steam shows complete; the site shows processing” is more useful than treating both systems as one record. Do not assume one support team can see the other team's internal history.

A request to send to a diagnostic account or approve a test trade is not a record lookup. Checking a Steam Trade URL is also different from handing over a password or authentication code. Valve's safe-trading guidance says money cannot be transferred through the Steam trade interface. A message describing an outside payment as if it were a Steam item does not prove the consideration, and Steam does not guarantee that payment.

Give Support what you confirmed and what you do not know#

The following is a hypothetical way to describe a problem, not a report of an actual outage. Put only what you directly checked in the brackets and leave unknown fields marked as unknown.

> On [date, time, and time zone], an error appeared while I was [creating an offer / accepting an incoming offer / confirming in the app]. The exact message was [text]. The offer currently appears in [list or history] with [status]. The trade record shows [item movement confirmed / normal lookup but no matching movement / lookup failed]. The item description shows [condition]. After that, I [action actually taken] and observed [result].

Separate what the other person told you from what your own screen shows. You can attach the relevant offer address to a private support request, but hide unnecessary account and email information from a public post. Passwords, authentication codes, login cookies, and recovery codes are not needed.

Choose the route closest to the failed step in official Steam trade support. If you suspect you have lost control of the account, stop ordinary retries and read the account-recovery section of the trade-safety guide. If only an outside site remains in processing, give that service the two records. Opening a support request does not guarantee a reply time or item recovery.