Why Is There a Mismatch Between the next_charge_scheduled_at Values in the SUBSCRIPTION Table and My Source Data?

Question

Why is there a mismatch between the next_charge_scheduled_at column values in the SUBSCRIPTION table and my source data?

Environment

Connector: Recharge

Answer

We incrementally update the SUBSCRIPTION table based on the data we retrieve from Recharge API's subscriptions endpoint. Specifically, we update the table when Recharge updates the updated_at field.

Recharge updates the updated_at field when you apply changes to a subscription's fields or attributes. However, Recharge doesn't update the updated_at field when the next_charge_scheduled_at field is updated. As a result, we don't update the SUBSCRIPTION table incrementally when the next_charge_scheduled_at data is updated.

The next_charge_scheduled_at value is associated with Recharge API's charges endpoint. Therefore, you can find a customer's up-to-date next_charge_scheduled_at value by going to the scheduled_at field of the CHARGE table and locating the applicable customer_id. Alternatively, you can execute the following query in your destination:

SELECT ID, CUSTOMER_ID, UPDATED_AT, SCHEDULED_AT, _FIVETRAN_SYNCED FROM RECHARGE.CHARGE
where CUSTOMER_ID={id} and PROCESSED_AT is null;