Skip to content

Troubleshooting

Start with the feature and the exact message shown. Keep useful received results before retrying a search.

SymptomWhat to check
No resultsCheck capitalization, literal versus regex mode, and query specificity
Matches disappeared after filteringClear the received-result filters
Invalid regular expressionUse RE2 syntax and remove unsupported constructs
Partial results or interrupted searchKeep useful received hits, then retry or refine
Daily search limit reachedCheck Your plan or wait for 00:00 UTC
Workspace unavailableOpen your workspace again and confirm you are signed in
SymptomWhat to check
No new matchesCheck active status, result cap, rule specificity, and whether relevant activity has been processed
Multiple content conditions never matchRequired text must occur on the same added line
Excluded paths still appearUse not contains inside an AND Match rule
Monitor creation is blockedCheck account-wide active capacity and use a workspace you own
No email for later matchesFirst-result email is a one-time notification
Search regex works but monitor regex differsThe features use different regex engines and case-sensitivity rules

Check the workspace, All/Saved/Ignored view, and filters before concluding that a result is missing. Use Refresh when you need to reload workspace records. A saved code-search excerpt can lack an author or update timestamp.

If a problem persists, include the feature, approximate time, status or error message, and whether any partial results arrived when contacting support.

The customer API has a separate error reference covering authentication, permissions, rate limits, and failures after a stream starts.

Contact GitHound with the affected feature, approximate time and timezone, error message, and steps to reproduce. Include whether results arrived before the interruption. Never include your API key, login session, or a suspected secret in a general support message.