Understanding charge_id Updates and updated_date Behavior in Subscription API

Overview

This article explains why updates to the charge_id field in a Subscription may not trigger changes to the updated_date field in the Subscriptions API response. This behavior is important to understand when performing incremental synchronization based on updated_date.

Background

Many integration workflows rely on the updated_date parameter to identify which Subscription records have changed since the last sync. Under normal circumstances, when a Subscription is modified through the standard UI or API workflows, the updated_date field is updated accordingly.

Observed Behavior

A scenario was identified where:

• A Subscription initially had a null value for charge_id.

• The charge_id was later added on the backend.

• The updated_date did not change, resulting in downstream systems missing the updated charge_id during incremental sync.

Root Cause

The update to charge_id was made directly on the backend (i.e., outside the standard Ordway UI/API workflow).
Because the record was not modified through the standard update mechanisms, the updated_date field was not triggered to update.

This behavior applies in all cases where data is modified via backend operations.