[SOLVED] Bars not printed and countdown stops (Schwab Data)

A

angoodwi

Well-known member
Joined
Mar 25, 2020
Posts
49
Likes
19
Hi All,

Latest Release 6.9.5 Ultimate Edition

This has happened to me with other data providers in the past, bars are loaded on initial display of a stock, index or futures.
However, after 5 minutes, 15 minutes no matter the time-frane used, the real time bars are not printed and the bar countdown stays at Zero.

Clearing local data, defining time zone and trading times doesn't resolve this.

Anyone experiencing such issue and how have you resolved it?

Many thanks.

Note:

S&P500 Index

Current Price: 5426.80 (Line)
Last Bar Close price: 5424.62
Bar counter: Stuck on 00.00

1723574367831.png

1723564319143.png
 
Last edited:
Update:

Seems like any instrument/symbol with $ appended is impacted, same for $NDX, $RUT, $TNX etc.
 
Not having a lot of luck with Schwab connection. I was getting error 400 not able to load 1min bars. Has anyone else had this issue? I got this error loading spy and qqq. It seems like indicators, specifically VWAP using historical 1min bars is causing issues.
 
This may have been resolved either cleared with data quality from Schwab or fixed in latest MW Bug Fix release 6.9.6 - monitoring it :)
 
Still getting these errors:
1726673103380.png
Im using version 6.9.7

When I try to change bar size I get this error:
1726673277446.png
 

Attachments

  • 1726673250200.png
    1726673250200.png
    10.7 KB · Views: 1
Yes I receive those errors from time to time and clearing local data for that instrument resolves it, annoying.

The issue I highlighted looks like was solved by MW. So question is whether this is data quality issue from Schwab e.g. time stamps on every data point/time zone or a MW bug still needs resolving....
 
Would also add, MW will always be dependent on the capacity, load balancing/performance and availability of Schwabs' API.
The errors relate to HTTP, so any end to end interruption of packet data can screw up the feed.

When you pay for dedicated services, they likely have more redundancy and bandwidth capabilities.. hard to say..
 
angoodwi said:
Would also add, MW will always be dependent on the capacity, load balancing/performance and availability of Schwabs' API.
The errors relate to HTTP, so any end to end interruption of packet data can screw up the feed.

When you pay for dedicated services, they likely have more redundancy and bandwidth capabilities.. hard to say..
Click to expand...
Thanks! I haven’t tried to clear local data yet so I will give that a shot.

Yeah, I never have issues with my CQG data. I haven’t had these issues with Tradestation daya either. Schwab connection must still be a WIP.

Thanks for the reply!
 
It looks like I'm only getting the error error 400 not able to load 1min bars on SPY and QQQ. I wonder if there is some type of data limit on the indexes? Does anyone have any idea what would be causing this? I'm using volume profiles and VWAP with standard deviation bands.
 
Last edited:
After a little more experimenting, it does it on all the ETF based tickers I’ve tried. SPY, QQQ, IWM, TLT, GLD, SLV. Hopefully, MotiveWave support will look into this. Might be a Schwab API issue.
 
You must log in or register to reply here.
Top