This came up yesterday, when one of my colleagues was using tap-redshift with target-stitch, running under Knots. It errored out on the target side with this message (among the other pieces of a schema error):
CRITICAL #/_sdc_batched_at: [2018-08-30T19:48:57.974000] is not a valid date-time. Expected [yyyy-MM-dd’T’HH:mm:ssZ, yyyy-MM-dd’T’HH:mm:ss.[0-9]{1,9}Z]
Thought I'd open up an issue to track this. The Singer Best Practices suggest RFC3339 as the format for date-times that are emitted by taps, and Stitch's Import API actually requires this.
rflprr
commented
6 years ago 
This came up yesterday, when one of my colleagues was using
tap-redshiftwithtarget-stitch, running under Knots. It errored out on the target side with this message (among the other pieces of a schema error):Thought I'd open up an issue to track this. The Singer Best Practices suggest RFC3339 as the format for date-times that are emitted by taps, and Stitch's Import API actually requires this.