Event-providers-don-t-update-Earnings-intermittently

At first glance, I think this may be by design. To avoid significant performance decrease caused by enabling event providers during regular data updates, Wealth-Lab would update event items in a smart way. Event items that can occur at any time like company news or splits are requested every time but those like earnings are not.

This has proven to be a solution against event provider updates slowing down backtests. But we've made a change in B34 to make even less requests for earnings. If this has become a bottleneck, let's see if unrolling the change for B36 that I've just done alleviates the issue.

QUOTE:
This [conservative updating approach] has proven to be a solution against event provider updates slowing down backtests.

Clearly there's a tradeoff between timely updates and the speed of the backtesting. Probably the best solution is a smarter compromise solution because it's going to depend on the strategy involved.

1) Add a check box to each strategy called "timely fundamental updates/slower backtesting". Those strategies designed for "investing" where the fundamentals (earnings, P/E ratio, PEG ratio) are used for backtesting will want to check that box. Those strategies designed for "trading" (where fundamentals are not consulted during the backtest) will want to leave that box unchecked, which should be the default.

2) If a stock is manually brought up in a Chart or Strategy for inspection, the fundamental(s) should be forced to update for that specific stock regardless of the above check box setting.

I use WL primarily for trading so, although salient fundamentals are displayed on my strategies, they are not made part of the backtesting model. I simply manually check the displayed fundamentals to verify they aren't terribly bad before placing a trade.

QUOTE:
Event items that can occur at any time like company news or splits are requested every time but those like earnings are not.

It understandable that earnings do not need to be update as frequently as news, but at minimum they should be updated when a new data point is out. In the above example AAPL still does not include the earning data even 10 days after its recent earning date.

Another question is that if the earning is not getting updated, then why the file date keeps changing and get updated? (again as shown above)

And lastly, as a simple solution how about totally separating data updates from back testing and give the full control to the user? If the user needs to back test on the latest data, he/she must first update the desired data sets only in the "Data Manager", so each back test run will not require any data updates anymore hence no need to address the updates speed problems in back testing (something similar to WL6).

QUOTE:
It understandable that earnings do not need to be update as frequently as news, but at minimum they should be updated when a new data point is out.

The whole point is that WL can't know when a new data is out. This means that every item will have to be requested every time, nullifying the effect of speed optimization.

QUOTE:
And lastly, as a simple solution how about totally separating data updates from back testing and give the full control to the user?

No, it's not considered. No need in an option to "disable a poorly performing logic". It should rather work smoothly under the hood. So if there's a bug (apparently), we'll simply have to fix it. That's it.

Let's get back to your initial question and clarify: what "some" symbols are failing to receive the latest updates, only AAPL and PFE? Is this "intermittently" or "consistently" as it's not clear from your first post.

You're running B34 now so also let's see if there's any improvement on earnings updates from B35.

Thanks for the prompt follow-up and the fix. Looking forward to B36.