I added this integration to Supabase recently, and noticed that the count of subscriptions objects was off. It was virtually equal to our confirmed count of active subscriptions, but it included just a few canceled subscriptions.
This leads me to suspect that the initial subscriptions backfill did not include canceled objects, which seems plausible considering that the listing API for subscriptions mentions:
By default, returns a list of subscriptions that have not been canceled. In order to list canceled subscriptions, specify status=canceled.
My guess that this API is used by this engine without status parameter, and that the engine does not perform a second pass to list and backfill canceled subscriptions. The few canceled subscriptions that did get synced came from webhook events.
I added this integration to Supabase recently, and noticed that the count of
subscriptionsobjects was off. It was virtually equal to our confirmed count of active subscriptions, but it included just a few canceled subscriptions.This leads me to suspect that the initial
subscriptionsbackfill did not include canceled objects, which seems plausible considering that the listing API forsubscriptionsmentions:My guess that this API is used by this engine without
statusparameter, and that the engine does not perform a second pass to list and backfill canceled subscriptions. The few canceled subscriptions that did get synced came from webhook events.