---
schema_version: "1"
id: 9bfb72bece8f29ac894032ebebfebf4e6f3aecf1d2a5ea7cb9f523dd07d4770f
title: "Lifecycle Center Error: Unresponsive Lightning Page"
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/devops_center_troubleshoot_unresponsive_page.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.devops_center_troubleshoot_unresponsive_page.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 1b436bb7c772343b741aeef38a20c70d94a134d7602b753940fbc6501941f7f3
description: "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."
products:
  - Salesforce Platform
release: "264"
---
# Lifecycle Center Error: Unresponsive Lightning Page

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**

1. 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>`
2. Open the retrieved file and search the XML file for the name of the problematic component.
    
    For example, search for `your_namespace:componentName` in the file path force-app/main/default/flexipages/<Page\_API\_Name>.flexipage-meta.xml .
3. 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.
4. Save the .xml file.
5. Deploy the updated metadata back to your org by running this command.
    
    `sfdx force:source:deploy -m FlexiPage:<Page_API_Name>`
6. To verify the fix, open Lightning App Builder for the page you modified.
    
    The warning or error associated with the component is resolved.