Quote from AAAintheBeltway:
IB has suggested that the customer should have immediately called IB when he noticed the cancel stayed pink. I have to wonder what they would have been able to tell him, since the original order had disappeared into the counterparty's servers, not to emerge for 30 minutes. Probably all they could have said was, well it appeared to be marketable but we really don't know what your position is. I don't see how that helps him at all.
Should a client inquire about an order whose status is indeterminate (pink or light blue), we would:
1) know there is a possible problem,
2) run a trace process which would show us where the thing got lost
3) see it was sent to a bank/exchange but never ack'd as either executed or rejected
4) contact the exchange/bank to get a status
5) maybe get a fill report or maybe get black-holed by them since they might not be able to figure it out in real time (don't know how fast they are since we really haven't had the opportunity to test the situation) but would have at least registered the issue which would let them feel comfortable that we (IB et clients) were not using a time option on them.
When there is no concern about 'gaming' on errors, the party who is being asked for comp usually feels much more comfortable granting it. Remember, for every honest person out there, there is at least one who will act opportunistically.
Technology is always subject to failure so the technology owner would quickly go under if forced to warrant the performance without restricting that liability in some manner. Without doubt, the best way to limit liability is to put a clamp on the amount of time to report the error. IB looks carefully at the timeliness issue. So do forex banks and exchanges and ECNs. So does
your personal bank (read the small print on the General Conditions regarding reporting of errors). Putting the issue on the table in an unambiguous and "official" manner is always the best way to get grey area problems treated as favorably as possible.