Can someone share experience about what is prefered when editing an existing order?

Should I "cancel it and create a new one" or should I only "edit it" (for example the quantity or price)? What is easier to handle? What must be take into consideration? I think (correct me if I'm wrong), for the official orderbook or the broker, "editing a limit order" is the same as "cancel the limit order and create a new one", because the order is re-queued anyway. So when using the TWS API, it does also not make any differences if "(1) editing an order" or "(2) cancel it and create a new one": (1) = (2). Am I right? Or are there hidden costs (cancellation fee or editing fee) I'm not aware of?

Thanks for your feedback.

Thanks for sharing your experience, Pratik. I just tried AMZN and I was also able to receive data. Considering GOOG fundamentals are available in the app, not sure why they aren't available in the API. This might warrant a call to API support or entering a web ticket.

-Mark

On Sat, Feb 20, 2021 at 3:40 PM <praditik@...> wrote:

Hi Mark,

Message code 430 clearly means "No fundamental data available". This means there is absolutely nothing wrong with the code.?

However, it is intriguing how GOOGLE's fundamental data can be unavailable. I also received the same error for GOOG. While AMZN and other few stocks return data with same script.?

Thanks,
Pratik

Hi Mark,

Message code 430 clearly means "No fundamental data available". This means there is absolutely nothing wrong with the code.?

However, it is intriguing how GOOGLE's fundamental data can be unavailable. I also received the same error for GOOG. While AMZN and other few stocks return data with same script.?

Thanks,
Pratik

The other night, when all server farms were connected (I checked status in TWS and reset data connections multiple times), I have noticed that my LMT order was not executing while market price was matching it or even exceeding it.?The order was placed manually on TWS for a Forex pair. I am pretty certain results would have been the same if it was done through API. I could see that the order had a different color sign beside it (that was unfamiliar to me) and tooltip said IBKR did not acknowledge the order yet.

Given there was no connection issue between my TWS and IBKR, it seems that IBKR can at their own discretion - without any penalty to them - do one or all of below:
A) Delay some users order executions (by putting certain servers on maintenance and not other servers) while other users executions are processing (be it intentionally or not). This in effect gives some users access to working servers and others not which creates an unfair advantage.

B) Delay some or all users order executions while their own orders might be executed (i.e. if they are loaning user shares to other brokers or exchanges for short selling). Or they could be participating in Forex market as a corporation while user orders are not executed because they do no eat their own dog food and their own order route through different servers.

OR another scenario that might be happening is that:
C) IBKR's internal execution system is down for that particular security (or all types of securities) and sending process to external or internal exchange system does not work BUT they are showing data feed from exchanges which basically excludes their own exchange trading which is not happening at that time. This scenario is a maintenance issue of course and no trickery since no one is advantaged over another. It is the data that is placed through other brokers to their internal exchange or external exchanges but IBKR reflects them to their users while their order placement system is down.

My questions:
1) If C above happens, do they ever show an indicator for this issue in either TWS *charts (not order window) or through API that you have seen? Something like, "Oops your LMT is matching wide market price now but our systems are down to place it and execute it - we are sorry for our horrible service).

2) If A or B happens, isn't there a regulatory body that checks their tapes and goes well at this 5 minutes you as a corporation sent millions of orders while none of your regular user orders were sent to exchanges? Or is this too in-depth for the feds still and they don't have the technical knowledge to monitor these sort of trickeries or mistakes?

3) I have seen this happening with Forex (I think it was around reset time - 12:00 am; not that reset time gives them an excuse). Have you seen this happen with regular stock (or other securities) or Forex at any other time or in another scenario?

4) Have you noticed any other serious - out of whack - data streams or order issues that you have experienced? and how do you try to remedy them?

Thanks,

My CI testing follows what Mark outlines.??
My code is in Java.? I wrote a broker interface which limits the IB API pieces I use.? I then use a mock class framework (Mockito) to simulate responses.? This of course doesn't simulate TWS, but at least allows for testing of my code.

But sometimes weird things happen in production and TWS doesn't do what you expect, so an idea I had was to implement a TWS API "recorder" so I can record/replay IB API events to diagnose problems that come up in production.? Then use those event records to generate test cases.