Fix a failed Discovery run

Discovery runs can fail for a few reasons: an empty search, filters that discarded everything, a stuck background process, or a stage-specific error. This article maps each failure message to the fix.

Where failure messages show up

Failed runs surface in three places:

1. On the run detail page (/discovery/runs/<runId>) with a red status banner.
2. On the Discovery landing page in the Active & recent runs section as a Failed row.
3. In your Inbox as a Discovery notification.

Click the run to open the detail and read the exact message.

The failure messages you might see

"No companies could be found for this search query."

The search returned zero results. Almost always caused by a search profile that is too narrow.

Fix: open the profile and:

• Widen the Regions to include a bigger area.
• Widen the Company size band.
• Remove very specific Keywords.
• Loosen the negative brief (or drop it entirely for the next run).

Save the profile and run it again.

"There were {count} companies discovered, but none passed the quality filters."

Blake found candidates but every one of them scored below your plan's minimum threshold (see Understand discovery scores for the per-plan minSaveScore).

Fix: use the Analyze affordance on the run detail. It suggests concrete profile changes. Common causes:

• Your profile description is generic and produces borderline matches.
• The example companies you mentioned are outliers for your market.
• Your Golden Cases point at a different segment than the profile is asking for.

Update the profile and rerun.

"This run has been running for more than 15 minutes, that is not normal."

The background process stalled. Blake usually completes a Standard run in a few minutes.

Fix: click Stop run on the detail page, then start a new run with the same profile. If it stalls again, contact support at support@useblake.ai with the run ID.

"Discovery Credits exhausted"

You hit your Discovery Credit limit for the period. Every discovered prospect costs 150 Discovery Credits.

Fix: wait for the monthly reset, or ask an Admin to upgrade the plan at Settings > Billing. See Credit and rate limits for the details on how credits recover.

"Daily discovery limit reached"

You hit your per-day Discovery-run cap for your plan (2 on Free, 3 on Scout, 5 on Closer and up).

Fix: wait for tomorrow, or upgrade for a higher daily cap.

"Monthly discovery limit reached"

You hit your per-month Discovery-run cap for your plan (10 on Free, 25 on Scout, 50 on Closer, 200 on Dealmaker).

Fix: wait for the monthly reset (28 days after your last reset), or upgrade for a higher cap.

When a run partially succeeds

Sometimes Blake saves some companies but the run ends with a warning. This means:

• Some companies cleared your plan's minimum score and were saved to Prospects.
• Some companies were discarded because they scored below the threshold.

The counters at the top of the run detail show the exact split: Found / Scored / Enriched / Saved.

Open Prospects to review the saved companies. See Review and qualify prospects.

Prevent future failures

• Set the profile strength to Solid or Strong before saving. Blake's meter shows what is missing.
• Add Golden Cases so score calibration has real deals to lean on. See What a Golden Case is.
• Keep the negative brief short on early runs. Add specifics only after the first successful run.
• Check your credit balance in Settings > Usage before larger runs.

If nothing above fits

Send the run ID (visible in the URL and on the run detail) to support@useblake.ai with a short description of what you were expecting. Blake's support team can trace the failure to a specific error class.

FAQ