You are here:
Troubleshooting Quick and Custom Actions
Reference for diagnosing and resolving common Quick Action and Custom Action issues in Life Sciences Cloud.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise and Unlimited Editions with Life Sciences Cloud, Life Sciences Cloud for Customer Engagement Add-on license, and the Life Sciences Customer Engagement managed package. |
Action Appears on the Record Page but Not on the Home Page, Calendar, or Search
The Admin Console controls these locations, not page layouts. Add a Quick Action or Custom Action record with the appropriate Location field set.
Configured Actions Don't Appear on an Object
To turn on dynamic actions, from the Admin Console, select Mobile, then select Application Settings, then select Enable Dynamic Actions.
- If dynamic actions are on, only actions configured on the object's Lightning record page appear. Add actions to the Highlights Panel component on the Lightning record page.
- If dynamic actions are off, only actions configured in the object's page layouts appear.
Generate a new metadata cache after you make configuration changes.
Configured Custom Action Doesn't Appear on a Record Page
Custom actions require a corresponding standard action counterpart to appear on record pages. Create a standard action in Salesforce (Buttons, Links, and Actions), and add it to the object's page layout or Lightning record page.
Custom actions on custom pages, such as the home page and Next Best Customer, don't require a standard action counterpart.
Configuration Changes Don't Appear in the App
All configuration changes—quick actions, custom actions, and page layouts—require a new metadata cache to take effect. From the Admin Console, select Mobile, select Metadata Cache, and then select Create New Cache.
Custom Action Label Fails to Translate
Custom actions that appear on custom pages, such as the home page and Next Best Customer, use the MasterLabel as a custom label key (this behavior is a Summer '26 change). Create a matching custom label to provide a translation.
Custom actions that appear on record pages use the standard action's translated label instead. Configure the translation on the standard action counterpart.
LWC Action Doesn't Go to the Record Detail After Creation
This behavior is a current limitation of LWC in the Life Sciences Cloud mobile app. Because the server creates records directly, the app requires a round-trip sync before the record appears.
Translate a Quick Action Label for the Salesforce Mobile App
Create or use an existing custom label in your org whose API name matches the MasterLabel of the quick action record. The translated custom label appears automatically after a metadata sync.
The key used in the Life Sciences Cloud mobile app (MasterLabel) can differ from the key used on the desktop site (SObject + Action Name), so configure both separately.
