> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xpanse/inventory/upload-or-remove-assets/undo-an-asset-removal.md). # Undo an asset removal There may be situations where you want to add an asset back to your inventory that was previously removed. Cortex Xpanse will not allow you to upload an asset that was previously removed, but you can undo the removal to add that asset back to the inventory. A common use case for undoing a removal is when an IPv4 range has been removed, but you want to add back an IP address that falls within that range. In that case you can undo the removal of the range, and then submit a new removal request for the ranges before and after the IP address that you want to add back. For example, if you removed IP range 192.0.2.0 -192.0.2.24, but then realized you need to include 192.0.2.10 in your inventory, you would: 1. Undo the removal for IP range 192.0.2.0 -192.0.2.24. 2. Submit a new asset removal request that includes IP ranges 192.0.2.0 - 192.0.2.9 and 192.0.2.11 - 192.0.2.24 How to undo an asset removal 1. Navigate to **Settings** → **Configurations** → **Asset Management** → **Asset Uploads/Removals**. 2. In the **Asset Uploads/Removals** table, find the asset you want to add back to the inventory. An asset must be in the **Removed** state to undo the removal (and add it back to the inventory). 3. Right-click the row and select **Undo Asset Removal**. Click **Yes** to confirm the removal. After confirming the Undo Asset Removal action, the asset will no longer appear in the table. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-xpanse/inventory/upload-or-remove-assets/undo-an-asset-removal.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.