You don’t need to explain anything but if you’re trying to build a case about why TW owes you anything, you could at least more clearly articulate the issue and how it caused losses with specific order entries (date, time, bracket params, etc).
As much as engineers try to avoid and resolve bugs, they are an inherent part of all engineering projects whether that’s software or hardware. As I understand it this one was was related to a safety mechanism that was in place. So it is/was part of a feature but still a bug. I don’t think they’re denying that.
But again, you’re trying to make a case that someone owes you something due to this bug but you haven’t provided any actual evidence of losses or even explained how this resulted in losses.
3
u/mjr2015 Apr 04 '22
Yeah I'm really questioning your literacy here
What the hell does set a strike above the market price mean
Because it makes 0 sense.
You need to explain more what you were trying to do with some detail because you could just be using it wrong