Support Board

Date/Time: Sat, 10 May 2025 01:10:48 +0000

Post From: Sierra needs to handle IB pacing violations more gracefully

[2016-07-06 18:14:30] Link To Thread - Link To Post [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We checked and we verified that this cannot possibly be true: Now here is your second request: 10:04:33:526 <- 20-5-4--IBUS30- CFD-----SMART-- USD---0-49-1-20 -5-5-- You can see the difference. It does not have valid durations string or the end time. So this resulted in the error message you have received. Not at all. So this answer from Interactive Brokers is not correct as far as it being a problem with the client application request data being incorrect. The data is being made incorrect somewhere within TWS most likely. Furthermore, we verified that even this request which appears correct on their side: 10:04:25:024 <- 20-5-3--IBUS30- CFD-----SMART-- USD---0-2016071 6 23:59:59 GMT-1 day-11 D-0-MIDPOINT-1- does not represent the actual data being sent from Sierra Chart. Similar but different. So the corruption is on the TWS side. We are 100 percent certain of that. Interactive Brokers needs to solve this problem for you. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing