Summary
The user is experiencing an issue where the connector is using the last sync end_time instead of the last sync updated_at as the stream_interval start_time. They are trying to understand the cause of this behavior.
Question
<@U04SE163WC8> I’m using a cursor called updated_at and I added field on the connector to try to understand which {{stream_interval.start_time}} it is using.
The last updated_at from the previous sync was 2023-12-29 08:37:32 however the {{stream_interval.start_time}} was 2023-12-29 13:07:56 which matches exactly the {{stream_interval.end_time}} from the last sync.
What is causing this behaviour of using the last sync end_time instead of the last sync updated_at?
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.