Which connector: Clockify

Please add hard-delete capture for the Clockify TIME_ENTRY table (soft-delete via _fivetran_deleted = TRUE), as already supported for CLIENT, PROJECT, USERS, TASK, TAGS, WORKSPACE, etc.

Additional details:

-  When a time entry is hard-deleted in Clockify, the connector does not detect the deletion during normal incremental syncs. The corresponding destination row keeps _fivetran_deleted = FALSE and lingers indefinitely, so it stays in every downstream model until someone manually runs a full historical re-sync.

- Confirmed by Fivetran Support: delete capture is currently not supported for TIME_ENTRY (only for CLIENT, GROUPS, HOLIDAY, INVOICE, PROJECT, TAGS, TASK, USERS, WORKSPACE and their child tables).

- TIME_ENTRY is the highest-volume, most business-critical Clockify table — it drives all time/consumption reporting. Undetected deletes silently inflate every metric built on it.

Real example in our data (BigQuery destination):

• Time entry 6a5a80fa95204e6a92579c6b — a timer left running over a weekend (PT59H42M26S, ~59h42) — was deleted in Clockify by the user.
• It still exists in the destination with _fivetran_deleted = FALSE (_fivetran_synced frozen at 2026-07-20 while the connector otherwise syncs hourly).
• Result: a beneficiary's 30h plan is reported as 70h consumed — a false "red / over-budget" alert built entirely on a phantom row.

Periodic full re-syncs are a heavy, easy-to-forget workaround for a table that changes constantly; they don't scale as a permanent answer for TIME_ENTRY.