Dealing with inconsistent datetime formats in API responses for ChurnZero connector integration

Summary

Addressing synchronization issues in ChurnZero connector due to inconsistent datetime formats in API responses


Question

Hey, I’m working on integrating a vendor (ChurnZero) using the connector builder and have encountered synchronization issues due to some API responses containing invalid and inconsistant datetime formats. For example, some timestamps have seven fractional seconds, such as 2024-04-19T13:21:06.4643864Z, instead of the standard six. This discrepancy is causing sync failures as it doesn’t match the templates that I defined for incremental sync (ex: %Y-%m-%dT%H:%M:%S.%fZ). Could you recommend any strategies to address this issue? Thank you



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["churnzero", "connector-builder", "datetime-formats", "synchronization-issues", "incremental-sync"]