When an element has been removed but still appears when searching for it in OnBrand, this is usually due to the Solr indexes not having been correctly updated. Note that the Admin area in OnBrand and the Content module in Unify use Lucene for their searches, meaning they should be unaffected by Solr issues.

Prerequisites:

• Access to the EUW VPN.
• Access to Passwordstate.
• The names of the affected assets, as provided by the customer.

 Steps:

1. Access the Unify back-end for the customer, and head to Content > Indices. Note that some customers may have several groups of indices, such as Local and Remote. For a detailed overview of how to access each customer's environment, see Unify/OnBrand Customer Environment Details.
2. For each set of indices, you can check existing disparities at the bottom of the page. Select all the items that need to be reindexed by clicking on the checkbox to the left. For the reported issue, Brand Assets will need to be indexed.
3. Select Reindex items: keep existing index; refresh items for the given range and click submit. Note that you will need to repeat the process for each set of indices. In the image below we would need to perform the process for both Local and Remote indices:
   
4. If the issue persists after reindexing, you will need to repeat step 3, but selecting Rebuild index: drop existing index; rebuild from scratch. As this is a resource-intensive process, you should communicate with the customer to schedule a time to rebuild the indices that doesn't interfere with their normal operation. Again, ensure you run the process for all available index stores.

Note that indexing can be monitored under Configuration> System Information > Thread Monitor. Once the Content indexing queue reaches zero, all queued-up indexing activity has been completed.

Once the Content indexing queue under Configuration> System Information > Thread Monitor reaches zero, verify that the reported assets no longer appear when searching in OnBrand. Make sure that you perform these tests on the main dashboard, and not the Admin area. This is because, as mentioned before, the Admin area uses Lucene for its search.