Loading

Salesforce Lightning Component Changes Not Visible After Successful Deployment Due to Memcache

Udgivelsesdato: Jun 21, 2026
Beskrivelse

To improve performance, Salesforce Lightning components use Memcache (a server-side in-memory caching system) for caching component bundles. However, this can sometimes lead to stale cache issues, where users continue to see the old version of a Lightning component after a successful deployment.
Symptoms:

  1. You make a change to a Lightning component.
  2. You deploy the change to a sandbox or production org.
  3. After deployment, you access the Lightning component and observe that the old version is still in use.
  4. You may also see an error message similar to: "aura/componentNameA -- Error: This aura component bundle is referenced elsewhere in salesforce.com. Remove the usage and try again."
Løsning

 

The root cause of this issue is a stale Memcache entry for the Lightning component bundle on Salesforce's servers. To clear the stale cache, open the component in the Developer Console and make a trivial change — this forces Salesforce to regenerate the cache entry and pick up the newly deployed version.
Steps to clear the Lightning component cache:

  1. Open any Lightning component in the Developer Console (Setup > Developer Console).
  2. Locate and open the component that was recently deployed but is not reflecting the changes.
  3. Make any trivial change to the component file (for example, add a single whitespace character in a comment).
  4. Save the component (Ctrl+S / Cmd+S).

This forces Salesforce to clear the Memcache entry for the component bundle. The updated version of the component will load correctly the next time it is accessed.

     

    Vidensartikelnummer

    000381669

     
    Indlæser
    Salesforce Help | Article