Excel STOCKHISTORY() function repeatedly encounters #CONNECT! error.

Hmmm.

The problem seems to have been corrected on my system and all STOCKHISTORY formulas have worked correctly for the past several days on the same spreadsheets that had been giving the problem.
Having said that, I have noticed the responses to STOCKHISTORY occasionally, but rarely, are MIA, but they seem to recover normal operation after a minute or two. I have seen the occasional #SPILL!, but that can usually be traced to a problem in the spreadsheet. No other errors have been noticed.

You may want to check the Excel version you are using. I have Version 16.89.1 (24091630). I have also noticed an automatic MS Office update since then but don't know if that was to Excel or another app in the suite.
This is on a MacBook Pro using Sonoma 14.6.1

This is still a problem as of September 26.

I am very unhappy. The whole reason I upgraded to Office 365 was to use STOCKHISTORY. That worked fine for a while but has been failing recently. Based on the discussion threads, it appears to me that Microsoft is not handling this with any sense of urgency -- it has been a problem for almost a month and a half now -- WAY too long for something as financially important to as many people as STOCKHISTORY is.

I understand this is not a professional product, but (a) it is an advertised feature, (b) it has stopped working reliably, and (c) a month and a half to fix it is ridiculous -- especially for a financial product that people depend on. I understand that Microsoft says the problem is with their supplier. My response is: "Stop trying to make your problem be my problem!" Microsoft must own this problem, and they need to get urgent about getting it fixed! Microsoft's supplier is Microsoft's problem, so fix it! Now!

There must be something in the individual spreadsheet parameters that is triggering all the errors. I have two spreadsheets that use STOCKHISTORY. One of them uses STOCKHISTORY to update 54 symbols going back 3 years daily (call it S/S "A"). The other one uses STOCKHISTORY to update 5 symbols over a period of only the previous 5 days (call it S/S "B"). Both spreadsheets also use data type Stock symbols to retrieve current quotes.

S/S "A" seems now to be operating correctly without errors. It had been very bad for a couple of weeks. This has now been working correctly since 9/3.

S/S "B" has continued to give all the usual variety of errors every day. By reloading frequently, it has been able to get past most of the errors, but I have had to bypass several VBA macros to deal with the errors. Today, even that was not possible. Even the Symbol:Price returned was for yesterday's price, not today's; and the STOCKHISTORY function failed continuously.

I created a fresh spreadsheet containing just the 5 symbols and asking for today's quote. It worked fine. I went back to S/S "B" and tried again - still got yesterday's quote and failed STOCKHISTORY.

I then restored a backup of S/S "B" from yesterday when it mostly worked. That version did indeed give me today's quotes rather than yesterday but the STOCKHISTORY still failed.

So whatever Microsoft/Refinitiv did last week seems to have fixed my S/S "A" problems but has not helped with S/S "B" - a much less demanding spreadsheet

I guess it was just TGTBT. I did jinx it.

We're back to random #CALC!, #CONNECT!, #SPILL! and #VALUE! errors again, as well as "Excel ran out of resources while attempting to calculate one or more formulas. As a result, these formulas cannot be evaluated."

Even with a small spreadsheet with just 5 symbols and 5 days of quote history sought.

I hope this doesn't jinx it but holding my breath and crossing my fingers I've had no issues today with the STOCKHISTORY function. We've heard nothing from Microsoft as to whether they found the issues and fixed them. If this is so, it would be good to hear where the problems were.

A minor continuing gripe is that entering a new symbol in an existing cell designated as type "Stock" often results in the system defaulting to an exchange:ticker without bringing up the Selection window for user confirmation. This can result in a stock symbol unintended and needs diligence to prevent it messing up other things. This is an old problem.