I noticed the issue in May 2018, so getting my data in February was just in time for 2019 reporting (I had mixed up the timestamps when I originally wrote I got the data in April).