Skip to main content

Why do I see 'Cannot cancel order because order is not listed in open orders anymore'?

Resolve 'Cannot cancel order' errors by reconnecting API, checking rate limits, or manually removing orders in Cryptohopper.

Pete Darby avatar
Written by Pete Darby
Updated this week

There are various reasons why you might see 'Cannot cancel order because order is not listed in open orders anymore' in your trading bot output:

  • The trading bot has been turned off for a while, leaving an order open that was placed through Cryptohopper. If the trading bot is turned back on after a certain period, it may happen that the order ID can no longer be retrieved via your crypto exchange.

  • There has been a temporary disconnection from your crypto exchange via the API Keys or Fast Connect. This issue usually resolves itself automatically unless you see a message at the top of your Dashboard or Advanced Dashboard indicating there is a problem with your API Keys or Fast Connect. If this is the case, you will need to reconnect to your crypto exchange. Check our tutorials for all crypto exchanges on how to do this.

  • You have reached the rate limit for the number of API calls. This is uncommon but can happen during extreme activity on a crypto exchange. When using Kraken, we always recommend using 2 API Keys to ensure a higher API rate limit.

Steps to remove the stuck order from Cryptohopper

  1. Navigate to the Orders tab in your Cryptohopper dashboard.

  2. Locate the specific stuck order you wish to resolve.

  3. Instead of selecting "Cancel," click on the Remove button. This option clears the order from Cryptohopper without making changes to your connected exchange.

Cryptohopper trading interface showing ETH/USDC sell order details with Order ID 115659515. Features Action menu with Cancel order and Remove order options for managing stuck orders. Display includes order amount of 0.1005 ETH, rate of 3855, and manual trigger information. Interface demonstrates how to remove orders that can't be cancelled due to exchange API limitations or bot downtime.
Did this answer your question?