The error message “Invalid timestamp: ‘2020-06-08T13:15’” suggests that the timestamp format you’re using is not complete. It seems to be missing the seconds component. A complete ISO 8601 timestamp should look like this: 2020-06-08T13:15:00. If you’re getting this error during a sync operation in Airbyte, it could be due to the source data not having a complete timestamp. You might need to adjust the data at the source or use a transformation step to ensure the timestamps are in the correct format. If you’re using a database as a source, you might need to adjust the way you’re extracting the timestamp data. If you’re using an API, you might need to adjust the way you’re parsing the timestamp data. In the case of a forum post about a similar issue with the Amazon Seller Partner source, the user suspected that the issue was due to the ISO 8601 date formatting. The colon (
in the date was being changed to %3A. If you’re experiencing a similar issue, you might need to adjust the way you’re encoding the timestamp data. Source: Forum Post: Invalid Timestamp in basic normalization (source-postgres) Forum Post: 
SOURCE: Amazon Seller Partner - Error: InvalidInput - ISO 8601