From what I can see in the log:
Since commissioning your IoTaWatt you have been uploading to Emoncms, beginning on April 10, 2019.
With respect to Emoncms.org, everything went smoothly for about 21 months. There were various issues and restarts which recovered as expected, uploaded history, and pressed on.
For whatever reason, on January 19 this year at about noon, you stopped the uploader, changed the URL to address a local instance of Emoncms, and restarted the uploader.
Long story short, you were able to upload your current log history to that instance and it appears the hole occurred during the end of that upload. My suspicion is that it has something to do with restarting the Emoncms instance.
Private instances of Emoncms, as opposed to the enterprise Emoncms.org, use Redis to hold the inputs database in memory. On restart, they are lost and so cannot respond to IoTaWatt’s query with the time of last input. As a result, IoTaWatt starts uploading from the current time.
IotaWatt to EmonCMS reload - #17 by overeasy
So I think that’s what happened. Not sure how to recover. I don’t believe it’s possible with the tools available in Emoncms.
Question: Why did you switch from Emoncms.org? It appears to have been working fine for a year and a half. If you have not changed anything, you should be able to simply reset your uploader to Emoncms.org and it should pick up where it left off at about noon on January 19th.