Hi - the history table was updated again last night per the twitter update @betwiser, here:
Basically, the table needs to be reinstalled whenever the database schema changes. In this case, the new "month" field was showing as an integer value when in fact the value is the text month, eg. January as opposed to 01.
Since there are over 200 new fields now there may be a few bugs that need ironing out, hence the reason for the updates, although of course the intention is to avoid this and stablize the new tables as soon as possible.
Usually you can assume that if you have any error messages that refer to either historic_runners_insights or the daily_runners_insights tables that the data needs to be downloaded and re-installed due to a schema change. NB. We will also be posting on twitter if this is the case, for the avoidance of doubt.