Run History
Revisit past searches and results.
Run History
How to Track and Reuse Past Searches in Beesla
Run History lets you see, review, and learn from past searches you’ve run in Beesla. It gives you visibility into what you searched for, what results were returned, and how your sourcing strategy has evolved over time.
This page explains how Run History works and how to use it to avoid duplicate effort and unnecessary token usage.
What Run History Shows
Every time you run a search, Beesla records it in your workspace.
Run History includes:
- The role description or job description used
- When the search was run
- The number of results returned
- Candidates added to your CRM from that search
This creates a permanent record of sourcing activity.
Why Run History Matters
Without history, teams tend to:
- Re-run the same searches
- Forget what inputs worked
- Waste time and tokens repeating mistakes
Run History helps you:
- Revisit successful searches
- Compare results across different prompts
- Understand how small changes affect outcomes
It’s a learning tool, not just a log.
Reviewing Past Searches
From Run History, you can:
- Open previous searches
- Review the candidates returned
- See which profiles were strongest
- Reuse ideas from effective prompts
Reviewing past searches does not consume tokens.
Once results are retrieved, you can revisit them freely.
Avoiding Duplicate Searches
Before starting a new search, it’s often worth checking Run History.
You may find:
- A recent search for the same role
- Candidates already saved in your CRM
- A prompt that only needs a small tweak
This helps prevent unnecessary reruns and keeps costs predictable.
Using Run History to Improve Prompts
Run History makes it easier to spot patterns.
Look for:
- Prompts that returned high-quality shortlists
- Prompts that returned too many results
- Prompts that were too restrictive
Use those insights to refine future searches.
Better prompts lead to better results and lower token usage.
Team Visibility
Run History is shared across your workspace.
This means:
- Teammates can see what searches have already been run
- Hiring managers can review sourcing activity
- Teams avoid working in silos
Shared visibility reduces duplicated work.
Common Misconceptions
“Reopening a past search costs tokens.”
It does not. Tokens are only used when new results are retrieved.
“Run History is just an audit log.”
It’s also a strategy tool.
What’s Next
To understand how search results are stored long-term: