Ex: when a subscription schedule is updated with a new "phases" object, fivetran just adds the phases and phase_plan into the tables without marking the previous phases and phase_plans as _fivetran_active=false or replacing them. There is no way to tell a subscription schedule update has occured because there is no historical context. I understand that historical data is not supported with every table for stripe, but if that can't be done, the second best thing to do is to replace the previous data with the updated data. The current implementation is not viable for accurately querying on the correct metrics and there is no way to track historical data with subscription schedule updates, which is a big issue.