@Kellie_Burton Please see the post I made last night regarding a similar error: New custom SQL SPICE import failures--recent code update?
Essentially, some combination of renamed fields and custom fields is causing column parsing to shift around. The datetime values themselves are unix timestamps directly from the query results, so they should work (and have worked for two years). This appears to be a pretty serious regression on Amazon’s side regarding SPICE import, but I’m not sure where else to escalate this.