Skip to main content

How to view search history

View your previous search runs and access cached results.

Written by Alice Jennings

Summary

To view your search history in MirrorWeb Insight, you can access a complete record of all your previous search runs, including their parameters, status, and cached results. This allows you to quickly re-access previous searches without re-running them.

Prerequisites

  • Login credentials to MirrorWeb Insight

  • Communications access permissions

  • At least one previously executed search

Step-by-Step Instructions

Step 1: Navigate to the Search page

Access the main Search section from the navigation menu to view your search options.

The Search page with the main search interface displayed

Step 2: Access the Search History section

Click on the History tab or Search History link to view your previous searches.

The Search History tab highlighted in the search interface

Step 3: Review your search history

Your search history displays in a table format showing search parameters, execution time, status, and result counts. Each row represents a previous search run.

Search history table showing previous searches with columns for search terms, date, status, and result count

Step 4: Access cached results

Click on any completed search entry to view the cached results without re-executing the search.

A search history entry being selected to view cached results

Recording: Complete flow showing navigation to search history, browsing previous searches, and accessing cached results

Recording: Complete flow showing navigation to search history, browsing previous searches, and accessing cached results

Notes

Note: Search results are cached in the system with a configurable time-to-live (TTL). Older searches may no longer have cached results available and will need to be re-executed.

Note: The search history shows all searches you have personally executed. You cannot view search history from other Compliance Analysts unless the searches were shared with you.

Important: Cached results reflect the data and configuration at the time the original search was run. If exclude phrases or other query-time settings have changed since the search was executed, the cached results may differ from what a new search would return.

Did this answer your question?