More efforts to handle stored start time to achieve the desired result.  The failure mode with the last attempt was an account where the registration date was in 2004 and it was hitting rate limit before it ever found a date with data.  Now it records the date it's about to try before it tries it, then in the case where there are any dates with data, either in the DB or from the data fetched within the loop, it overwrites the date with the max date with data.  It does that in the finally clause as well as after the normal end-of-loop.  This writes the attribute more than it probably needs to, but should hopefully work.