Why didn't my alert find a match?
When an alert runs but doesn't find a match, it can be frustrating. The most important tool for understanding why is the alert's Search History. Each "No Match" entry contains the AI's reasoning.
Here are the most common reasons an alert might not trigger a match:
1. The Alert Condition is Too Vague or Too Strict
This is the most common reason. The AI needs clear, specific instructions.
Too Vague: An alert for "new product launch" might fail because the term is too broad. Does "launch" mean an announcement, a website update, or a press release?
Too Strict: An alert for "Acme Corp. announces version 2.1 of their 'X-1' software" might fail if the announcement calls it "version 2.1.0" or just the "X-1 update".
Solution: Review the AI's reasoning in the search history. It will often tell you what it found and why it didn't meet your exact criteria. Try to rephrase your Alert Condition to be more precise but flexible.
2. The Search Timeframe is Incorrect
If your condition is about a recent event, but your Search Timeframe is set to "Last 90 Days," the AI might find an old, irrelevant article that technically matches your keywords but is not the recent news you're looking for. Conversely, if your timeframe is too short ("Last 24 Hours"), you might miss an announcement from two days ago.
Solution: For news-related events, "Last 7 days" is usually the best setting. For historical or foundational information, you might need "All Time," but use it with caution.
3. The Information Doesn't Exist (Yet)
Sometimes, the simplest answer is the right one: the event you're monitoring hasn't happened yet, or at least hasn't been written about on the public web within your specified timeframe.
Solution: Be patient. If you expect an announcement, ensure your alert is active and the schedule is set appropriately. You can always use the "Search Now" button to check on-demand.
4. The Source is Inaccessible or Blocked
In rare cases, a website might block automated systems like our AI agents, or the content might be behind a paywall or login screen that the AI cannot access.
Solution: Check the source URL provided in the search history. If you can't access it either, the AI likely can't either. If you need to monitor a source that requires a login, you may need a Custom Data Tool.