Troubleshooting

Troubleshooting

How to Fix Common Issues in Beesla

This page helps you diagnose and resolve common issues when using Beesla. Most problems fall into a small number of patterns related to search input, token usage, or access permissions.

Start here before contacting support.

I’m Getting Too Many Results

If a search returns too many candidates, it usually means the role description is too broad.

Try:

• Adding seniority (junior, senior, staff)
• Adding required technologies or experience
• Adding explicit exclusions (“avoid”, “exclude”, “not”)

Smaller, more focused result sets improve quality and reduce token usage.

I’m Getting Too Few Results

If a search returns very few or no candidates, the prompt may be too strict.

Try:

• Removing one nonessential requirement
• Broadening experience slightly
• Removing industry constraints

Make one change at a time, then rerun.

My Results Don’t Match the Role

If candidates feel off:

• Re-read the role description you entered
• Check whether priorities or exclusions were clear
• Look at the fit explanations for patterns

Refining the prompt usually fixes this faster than manual review.

I Used More Tokens Than Expected

Common reasons include:

• Very broad searches returning many results
• Rerunning searches without adjusting input
• Multiple users running searches

To investigate:

• Check Run History
• Look at result counts per search
• Confirm who has permission to run searches

Remember: tokens are charged per result returned.

A Team Member Can’t Run Searches

This is usually a role issue.

Check:

• The user’s assigned role
• Whether their role allows running searches

Only Owners and Recruiters can consume tokens.

I Can’t See Data Someone Else Added

Make sure:

• You are in the same workspace
• You are logged into the correct account
• The data was added to the CRM (not just viewed)

All workspace data is shared by default.

Something Looks Wrong With Usage or Data

If something still seems incorrect:

• Gather the search name or timestamp
• Note how many results were returned
• Identify which action caused the issue

Contact support with those details for faster resolution.

What’s Next

If the issue is about:

• Costs → see Tokens and Billing
• Access → see Teams and Access
• Search quality → see Natural Language Search

If it’s not covered here, contact support.