Loading
Upcoming Mandatory Changes to Public Key Infrastructure (PKI)Read More
Salesforce Enforces New Security Requirements in Summer 2026Read More

Action Launcher and provider search slow to load in Lightning

Publish Date: Jun 25, 2026
Description

This article addresses slow load times for the Action Launcher and Provider Search in a Salesforce Health Cloud environment running Lightning Experience.

You see the Action Launcher spinner persist for several seconds before deployable actions appear, and Provider Search results return slowly or display differently between two users on different machines or browsers.

Customers describe this as: "action launcher is taking time to load in health cloud environment" and "provider search sync is slow and inconsistent between different machines and browsers."
The symptom appears most often on record pages that host many Lightning components, large related lists, or Action Launcher deployments configured with many recommended/quick actions, and is more pronounced for users on lower-spec machines, older browser versions, or with full browser caches.

Resolution

Cause 1: Action Launcher loads slowly because of too many or unfiltered deployed actions.

1. Go to Setup > Action Launcher > Deployments.

2. Open the deployment assigned to the affected record page and review the recommended and quick actions list.

3. Remove actions the page does not need so the deployment contains only actions relevant to that object.

4. For each remaining action, set scope so it appears only where required: open the action and set the entry context to the specific object and record type instead of all objects.

5. Confirm the Action Launcher Lightning component appears only once per Lightning page in Setup > Lightning App Builder; remove duplicate instances.

 

Cause 2: Record page latency from component and related-list density.

1. Go to Setup > Lightning App Builder and open the affected record page.

2. Move noncritical components into collapsed accordion sections or secondary tabs so they load on demand, not on initial render.

3. For each related list, set [Number of Records] to 5 in the component properties.

4. Replace any filtered lookup fields used in heavily loaded sections; per Known Issue KI-35495, filtered lookups exhibit high latency. Remove the lookup filter or convert the relationship to a standard lookup where business rules allow.

 

Cause 3: Provider Search is slow or renders inconsistently across machines and browsers.

1. Confirm both users run the same supported browser and version; standardize on the current release of Google Chrome.

2. On each affected machine, clear the browser cache and reload, then retest. Inconsistent rendering between machines is typically a stale client cache, not a data difference.

3. Go to Setup > Health Cloud Settings and confirm Provider Search indexing is enabled so searches use the search index rather than live record scans.

4. Reduce the number of search filter fields evaluated on initial render; require the user to enter at least one filter value before results return.

 

Cause 4: Client and network factors.

1. Test the same page in an incognito/private window with no browser extensions; extensions frequently add render latency.

2. Test on a wired connection to rule out VPN or Wi-Fi latency.

 

Knowledge Article Number

005387724

 
Loading
Salesforce Help | Article