You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this your first time deploying Airbyte: No
OS Version / Instance: Ubuntu 20.04 on AWS EC2
Deployment: Docker
Airbyte Version: 0.35.31-alpha
Source name: Zendesk Support (0.1.12)
Destination: Snowflake (0.4.15)
Step where error happened: Sync job
Severity: High, as it forces to use the overwrite sync to have accurate data
Current Behavior
Hello,
On Zendesk Support, the incremental sync (shown as supported) doesn’t seem to actually work. Even using the incremental dedup + history sync, tickets don’t seem to be updated in my destination when they change (at least for their custom fields). I’m seeing discrepancies between the data in my destination, and data queried directly through the API, even right after a sync. This is a big issue, as it means we keep outdated information in the database...
Expected Behavior
Tickets in the tables should be updated, rather than being kept in a past state.
Logs
I'll provide logs upon request (for now, can't access the service because our VPN is down) - but not sure whether they would be useful - the sync job is successful, just not incremental with deduped as it should be...
The text was updated successfully, but these errors were encountered:
@alexchouraki let me ask you, did you try to update the connector version to the latest available? You use the old version 0.1.12 and we now have 0.2.6. You can update the connector's version in Settings > sources.
bazarnov
changed the title
Zendesk Support - Incremental Deduped sync does not work with custom fields
🐛 Source Zendesk Support: Incremental Dedup sync does not work with custom fields
May 26, 2022
Is this your first time deploying Airbyte: No
OS Version / Instance: Ubuntu 20.04 on AWS EC2
Deployment: Docker
Airbyte Version: 0.35.31-alpha
Source name: Zendesk Support (0.1.12)
Destination: Snowflake (0.4.15)
Step where error happened: Sync job
Severity: High, as it forces to use the overwrite sync to have accurate data
Current Behavior
Hello,
On Zendesk Support, the incremental sync (shown as supported) doesn’t seem to actually work. Even using the incremental dedup + history sync, tickets don’t seem to be updated in my destination when they change (at least for their custom fields). I’m seeing discrepancies between the data in my destination, and data queried directly through the API, even right after a sync. This is a big issue, as it means we keep outdated information in the database...
Expected Behavior
Tickets in the tables should be updated, rather than being kept in a past state.
Logs
I'll provide logs upon request (for now, can't access the service because our VPN is down) - but not sure whether they would be useful - the sync job is successful, just not incremental with deduped as it should be...
The text was updated successfully, but these errors were encountered: