The check for records left behind by a key change skips customers #42
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: wiki-cafe/member-console#42
Reference in New Issue
Block a user
What a person cannot do today
See which customer mappings point at records the current Stripe API key cannot reach. The check that runs after a key change reads back every synced product and price and marks the ones it cannot find as stale. Customer mappings are not read back at all.
What they should be able to do
Have the same check cover customer mappings, so a mapping that names a record from another Stripe environment is reported rather than found by a member.
Why it matters
A mapping recorded in the other mode is already caught without a read, because the mode recorded on the row disagrees with the key and checkout creates the customer again. A move between two test environments leaves both sides reporting test, so a customer id from the old one stays marked synced until that member's next checkout fails on a missing resource.
Where
The environment-check activity in the Stripe integration's workflows, beside the product and price loops; the customer mapping table in that integration's store.
Done when
The check reads customer mappings back under the current key, marks the unreachable ones stale, and counts them in the result the Stripe integration page shows.
Migrated from status/issues.md at
b7a0e15