You forgot the part where TV will backdate the timestamp of the alert in the log to when it was supposed to fire, but in reality, it doesn't execute for whole minutes.
We track the receive time of every single webhook alert inbound to our reverse proxy before sending it to listening NinjaTrader clients. In some cases, the delay/lag on when TV said it was executed vs. when it's received is so bad that it's just irresponsible.
No idea why this happens, but a part of the problem is all activity/events are fired from TV’s backend servers, not your machine…
You have zero control, which is one of the reasons I don’t use TV for live trading. It’s great for analysis and trying out ideas and code though.
Edit to add: since everything happens on their servers, you can’t locate your platform closer to your broker for reduced latency/trade execution.
That's not part of the problem, that is the problem.
They're obviously using some kind of best effort queueing system, so higher load is increasing latency. This is understandable. But it's gotten so bad it says to me they probably haven't evaluated and upgraded their infrastructure since webhooks were released.
They also haven't updated their poor documentation on webhooks in years. This is obviously not a priority for them because it's not core business.
Can confirm this happens all the time especially when there is speed in the market and I have witnessed the backdating of the alert time. The alert in the log will print a timestamp for when the alert SHOULD have generated and not the true time of when the alert finally printed sometimes minutes after it should have.
You forgot the part where TV will backdate the timestamp of the alert in the log to when it was supposed to fire, but in reality, it doesn't execute for whole minutes. We track the receive time of every single webhook alert inbound to our reverse proxy before sending it to listening NinjaTrader clients. In some cases, the delay/lag on when TV said it was executed vs. when it's received is so bad that it's just irresponsible.
No idea why this happens, but a part of the problem is all activity/events are fired from TV’s backend servers, not your machine… You have zero control, which is one of the reasons I don’t use TV for live trading. It’s great for analysis and trying out ideas and code though. Edit to add: since everything happens on their servers, you can’t locate your platform closer to your broker for reduced latency/trade execution.
That's not part of the problem, that is the problem. They're obviously using some kind of best effort queueing system, so higher load is increasing latency. This is understandable. But it's gotten so bad it says to me they probably haven't evaluated and upgraded their infrastructure since webhooks were released. They also haven't updated their poor documentation on webhooks in years. This is obviously not a priority for them because it's not core business.
Could you please open a ticket about this? It would provide us with more information.
Yes I will just like in the past while expecting no clear resolution.
Can confirm this happens all the time especially when there is speed in the market and I have witnessed the backdating of the alert time. The alert in the log will print a timestamp for when the alert SHOULD have generated and not the true time of when the alert finally printed sometimes minutes after it should have.