Sharadar Fundamentals load time

HI Brian,

I have a question about the load time of Sharadar Fundamentals. Lately, it takes quite a while to load the data for the daily update. For some reason, the entire history gets reloaded every night vs. a quick incremental load. It takes quite a while to update. Do you know what the issue could be or how to fix it?

Here is a sample of the log post the update command:

#{'status': 'successfully set Quandl API key'}

collect_sharadar_fundamentals(country="US")


quantrocket-fundamental-1|checking Quandl permission for SHARADAR/SF1
quantrocket-fundamental-1|/opt/conda/lib/python3.11/site-packages/urllib3/util/retry.py:83: DeprecationWarning: Using 'Retry.BACKOFF_MAX' is deprecated and will be removed in v2.0. Use 'Retry.DEFAULT_BACKOFF_MAX' instead
quantrocket-fundamental-1| warnings.warn(
quantrocket-fundamental-1|Quandl permission validated for SHARADAR/SF1
quantrocket-houston-1|172.18.0.10 - - [05/Mar/2026:17:13:22 +0000] "POST /fundamental/sharadar/fundamentals?country=US HTTP/1.1" 202 68 "-" "python-urllib3/1.26.18"
quantrocket-fundamental-1|checking Quandl permission for SHARADAR/SF1
quantrocket-fundamental-1|/opt/conda/lib/python3.11/site-packages/urllib3/util/retry.py:83: DeprecationWarning: Using 'Retry.BACKOFF_MAX' is deprecated and will be removed in v2.0. Use 'Retry.DEFAULT_BACKOFF_MAX' instead
quantrocket-fundamental-1| warnings.warn(
quantrocket-fundamental-1|Quandl permission validated for SHARADAR/SF1
quantrocket-houston-1|172.18.0.18 - - [05/Mar/2026:17:13:24 +0000] "POST /flightlog/handler HTTP/1.1" 200 5 "-" "-"
quantrocket-flightlog-1|2026-03-05 17:13:24 quantrocket.fundamental: INFO Collecting Sharadar US fundamentals
quantrocket-fundamental-1|Sharadar US fundamentals for 1990 are already up-to-date
quantrocket-fundamental-1|Sharadar US fundamentals for 1991 are already up-to-date
quantrocket-fundamental-1|Loading Sharadar US fundamentals for 1992
quantrocket-fundamental-1|Loading Sharadar US fundamentals for 1993
....

Based on how the source data API works, whenever a stock has a new filing added to the dataset, the stock's entire history gets flagged as "updated" and thus the entire history gets re-collected. This means that, during earnings season, you will usually be pulling the entire dataset on most days. Unfortunately this is beyond my control. The best approach is to schedule the daily update on your crontab at a convenient time so that the data is ready when you need it.