Trashed Linear tickets never appear as deleted or trashed
AnsweredWhich connector?: Linear
Additional details: I submitted a ticket to Fivetran because trashed Linear tickets never appear as trashed in our data. I was requested to submit a follow up feature request because the Linear syncs are functioning as expected. This is the response from Fivetran.
The Linear connector currently performs incremental synchronisation using the
updatedAtfield. However, when an issue is archived/trashed in Linear, those fields get updated, whileupdatedAtremains unchanged.
As a result, once the connector has synchronised an issue and advanced its incremental cursor, any subsequent archive event falls outside future incremental sync windows. Since the connector never re-fetches that record, the archive/trashed event is not detected and_fivetran_deletedand other fields are not updated, leaving stale records in the destination.
Ideally, I do not need to constantly resync the entire table, as this adds a lot of overhead. It would be great to have a solution in which the trashed tickets are automatically detected and marked as trashed.
-
Official commentHi Yue,Thank you for the clear description of the problem. We have added automatic detection of trashed and archived Linear issues to our active backlog. We have confirmed the source API exposes the archived and trashed state, so stale records can be flagged without full re-syncs. We will keep you updated on this thread as we make progress.Best,Syead Mujtaba Imam Rizwi
Please sign in to leave a comment.
Comments
1 comment