Troubleshooting ApolloError When Editing Plans or Prices

An ApolloError in the Memberstack dashboard typically occurs when an update fails because it attempts to modify billing settings that are permanent in Stripe, or because the underlying Stripe price or product was modified or archived outside of Memberstack.

Section A: Why This Error Occurs

1. Immutable Stripe Price Data:
   Stripe does not allow you to change the currency, amount, or billing interval of a price after it has been created. Because Memberstack stays in lockstep with Stripe, attempting to edit these fields on an existing price causes the Stripe API request to fail, which the Memberstack dashboard reports as an ApolloError.
   
    
2. Mismatched or Archived Stripe Records:
   If a product or price was deleted, archived, or disconnected directly from within your Stripe dashboard rather than inside Memberstack, Memberstack's attempt to sync changes will fail because the reference no longer exists in Stripe.

Section B: How to Resolve the Error

Rather than modifying an existing price, create a replacement price:

Step 1: In your Memberstack dashboard, click Plans in the left navigation and select the plan you want to update.
Step 2: Scroll to the Prices section and click Add Price.
Step 3: Enter your new billing amount, currency, and interval, then save the price. Memberstack will generate a new Price ID starting with prc_.
Step 4: Locate the old price in the list, click its vertical ellipsis (⋮) button, and select Archive. This prevents any new visitors from purchasing the old price.
Step 5: In Webflow, select your pricing button and update the relevant custom attribute with your new Price ID: 
data-ms-price:add = "prc_your_new_price_id"

What happens to existing members:
Members currently subscribed to the old price are not interrupted. They remain active at their original rate until they cancel, their subscription lapses, or they upgrade to a new plan.