Error-getting-daily-MU

Historical Providers > IB (should be checked) > right click > Clear Internal Request Tracking
Then open a new chart and try the request again.

Same error.
Also tried restarting WL after clearing requests.

Any Log Viewer messages for IB?

Works fine here -

There's really not enough information given in this discussion to diagnose this problem. For example, if the historical provider (IB) is writing MU data to disk when WL crashes (e.g. power or internet failure), then the file caching the MU data to disk will be truncated and corrupted. But I can't tell from this discussion if that is what's happening because not enough details are given. We need more details.

Is MU for the Daily scale the only stock misbehaving? Are all other stocks for the Daily scale working fine? Does your computer (or WL) crash frequently?

Hello Cone,

There is a log viewer error registered at first:
5/12/2026 05:44:13:013 Interactive Brokers
Interactive Brokers Broker: 05:44:13.01 162: Historical Market Data Service error message:Query failed: MU

After the first, above, log, no new log is registered.

No daily MU.QX cache file exists.
No problem getting other tickers on any bar interval, including daily. Again, MU works on other bar intervals, just not daily.

Please let me know if there is more diagnostics I can share.

p.s. no crashing issue...

Check IBContracts.txt. Does the record for MU match this?
MU=MU|USD|STK|SMART|NASDAQ

Check Markets & Symbols > Symbols
Do any of the Symbol records match "MU" (e.g., MU, M#, or ##)?

Yes:
MU=MU|USD|STK|SMART|NASDAQ
No, I don't see MU## in symbols
Does the fact that the error appears only on Daily indicate what the underlying issue might be?

One symbol.
One scale.
One computer. (Do you have another?)

That's a pretty unique problem.

QUOTE:
No daily MU.QX cache file exists.
No problem getting other tickers on any bar interval, including daily. Again, MU works on other bar intervals, just not daily.

Well, there's "something" on your disk that's preventing MU.QX from being created. Perhaps it's time for the nuclear option. Go to the Interactive Brokers historical provider icon, right click it, then select "Delete local files".

Deleting local files is a bad thing to do for IB because they have quota limits. Repopulating those local files will probably put you up against those quota limits. Perhaps you should wait until the end of the trading day to do it. But you need to do something to reset what's creating this problem.

It's a pretty weird problem, but the nuclear option has no place in solving it.

Well, restarting WL doesn't clear the problem, so the "bad condition state" remains on his local disk.

@Cone
Are you recommending he deletes all files related the the IB broker extension to clear this problem? Is there a specific file for the IB broker extension that should be deleted?

Is the connection to the IB data server stateless?

UPDATE:
If it "remembers" past session states, let me suggest that the IB broker extension resets the server session state automatically when WL starts up for the first time on a given trading day.

1. No, I said the opposite of that.

2. No. No.

WL is having the same exact problem with a brand new ticker (never used before) DGXX. Daily fails while 30 and 60 minutes work.
Other daily tickers, including brand new ones, are fine. No glaring messages in logs.

IBContracts.txt:
DGXX=DGXX|USD|STK|SMART|NASDAQ|DGXX|||1.7976931348623157E+308|

Again, looks fine for me - it even picked up the bid/ask with streaming after hours -



Let's start somewhere -
Give me a screenshot of your list of historical providers, showing IB and those above it.

Note SPY daily works.

There must be a reason in the Log Viewer if IB doesn't return the data for that request.

As an example that doesn't apply to this case, here's an attempt to request a "non Symbol" and the response -



At least we know that in your case, it's "finds" the contract, but just doesn't return data for some symbols, Daily only. Why? TBD.

Here is a fresh log after WL restart.
Initially, it's having an issue with ID 0 but is able to use an alternate ID.
I'm able to get streaming and other data without an issue.
I don't trade inside WL.
BTW, another ticker having the same issue: LUNR.