An alert describes a condition. A sell request asks for an action. A fill records an executed amount. These are three different kinds of evidence. A changing price can bring a position near an exit condition without creating a completed sale. Likewise, clicking a submission button does not by itself prove that the requested quantity has been sold.

In a position sell flow, Accepted means the request is awaiting confirmed fills. Pending confirmation means no fill has yet been confirmed to that flow. Read the words that follow the status rather than stopping at a reassuring first word. While the result is uncertain, keep the request reference and inspect its status instead of starting another sale to see whether that one works.

Filled, when confirmed by the server, is stronger evidence of execution. Even then, check the quantity and the matching records. Your original holding may have contained more than the amount requested. A confirmed sale of four units from a ten-unit holding leaves six units, assuming no other activity. Confirmation of a request does not automatically mean the entire original holding has disappeared.

Another message can say that the provider outcome was received while internal accounting is still pending. That means one part of the process has responded, but the app has not finished recording the result internally. The screen specifically tells you not to start another sale. Allow that request to be reconciled and check the relevant records; do not try to repair a display delay by creating another order.

A resolved request can also be described as ended with accounting confirmed. The accompanying wording matters: this does not necessarily mean the entire requested amount was sold. An ended order and a fully filled order are different outcomes. Use the executed quantity, any remaining holding, and the recorded status together to understand what actually finished.

If the request was not confirmed, or the browser closed before you saw the outcome, use the available Saved sell requests recovery flow. Its Check status or retry same request action is designed around the original request and amount. Do not clear saved requests to manufacture a fresh attempt. Recovery can be blocked when identity or account evidence is missing; read that message and return to the original context.

Closing a dialog after submission is not the same as cancelling an exchange order. A connection error is not proof that nothing happened, either. In Live, compare with the connected exchange's order and fill records when necessary. If the app received a status but failed to refresh the portfolio, treat that as a reconciliation problem rather than assuming the sale itself failed.

For any outcome, ask three questions. What was requested? What amount is confirmed as executed? What still needs an update or a status check? Those questions work for successful, partial, and uncertain results. They help you stay precise without needing to understand the software behind the scenes, and they prevent a confusing message from turning into an accidental duplicate action.