Why Are Conversation Records Marked as Deleted from the Parent Table While Child Entries Remain?

Question

Why are some conversation records marked as deleted (_fivetran_active = FALSE) in the CONVERSATION_HISTORY table while their related entries still exist in the CONVERSATION_PART_HISTORY table?

Environment

Connector: Intercom

Answer

This behavior is expected. Deletions in the CONVERSATION_HISTORY table are captured through Intercom webhooks, but those webhook events do not cascade to related child tables. When you delete a conversation in Intercom, only the corresponding record in the CONVERSATION_HISTORY table is updated, and its fivetran_active column is set to false. Related records in child tables, such as CONVERSATION_PART_HISTORY, aren't updated and remain unchanged.