When you access a Lightning page in Lightning App Builder, you receive a warning message: "You can't add a runtime_alm_devops:{component_name} component there." If you dismiss the warning, the page becomes unresponsive, and you can’t make any further edits.
Cause
This error appears because a runtime_alm_devops component, such as
runtime_alm_devops:activatePipeline is no longer available in your org. If
you had previously added this component to a page, editing that page now results in an error
because there’s no correct reference to the component.
Action
-
Run the command in your terminal to retrieve the metadata for the specific Lightning page.
Replace
<Page_API_Name>with the actual API name of your page.sfdx force:source:retrieve -m FlexiPage:<Page_API_Name> -
Open the retrieved file and search the XML file for the name of the problematic
component.
For example, search for
your_namespace:componentNamein the file path force-app/main/default/flexipages/<Page_API_Name>.flexipage-meta.xml . -
Locate the
<componentInstance>block that surrounds the component name. Delete the entire block from the opening tag to the closing tag.Make sure you delete only the specific
<componentInstance>block. Don't leave empty lines or break the surrounding<flexiPageRegions>tags. - Save the .xml file.
-
Deploy the updated metadata back to your org by running this command.
sfdx force:source:deploy -m FlexiPage:<Page_API_Name> -
To verify the fix, open Lightning App Builder for the page you modified.
The warning or error associated with the component is resolved.