The big account at initial fetch indicated 116000 v 190750 results to be retrieved without the control. By the time the run is finished, the 116K will surely be a different number with the coming and going in the meantime.

Edit: Just finished a pass w/o and got 173K as ResultsAvailable. Started the next and got RA of 96K, which kind of equates to Valid for this period + PV + Valid of previous period and an assorted set of valid, error, no reply, which are happily passing with the ReceivedTime Field absent... the records are happily written with the RT field left blank, Outcome=4. Will mark the respective thread as [RESOLVED], if you could do same for this one, as my permission has expired, were good on these 2 API issues.

Edit 2: The last w/o FDS=0 needed 51 minutes to work through, substantial time spent on extending tables, evaluating result state and deleting the superfluous. The w/ FDS=0 took just 15 minutes. that's a factor 3.4 quicker. Whilst it started off by determining ResAtStart for ResultsAvailable as 96K, by the end the last showed 94K, i.e. ad interim, in those 15 minutes, at least 2K changed state to FDS > 0. The secondary effect is that chances of misses largely reduced. On my own crunching account, not had a period miss since weeks and weeks. With this new option, the run from start to finish, prodcing the summary took just 9 seconds, for the 985 result meeting the criteria.

(But I'm still getting the periodic page 1 time-outs even well before the USA wakes up.)