I recently came across an issue using the generic db ETL. The issue is that the data being imported is in UTC and the last counter appears to store local time. The data being extracted is not always available right away and this has resulted in up to 4 hour gaps in my data. I am having to constantly reset the last counter an manually rerun the ETL to get the missing data. I am rewriting my ETL SQL query to convert the UTC time stamp into local time but it would be much easier and I believe useful if we could indicate the the source data time zone in the ETL and let BTCO handle the offsets.