Troubleshooting
Start with the feature and the exact message shown. Keep useful received results before retrying a search.
Troubleshoot Search
Section titled “Troubleshoot Search”| Symptom | What to check |
|---|---|
| No results | Check capitalization, literal versus regex mode, and query specificity |
| Matches disappeared after filtering | Clear the received-result filters |
| Invalid regular expression | Use RE2 syntax and remove unsupported constructs |
| Partial results or interrupted search | Keep useful received hits, then retry or refine |
| Daily search limit reached | Check Your plan or wait for 00:00 UTC |
| Workspace unavailable | Open your workspace again and confirm you are signed in |
Troubleshoot Watchdogs
Section titled “Troubleshoot Watchdogs”| Symptom | What to check |
|---|---|
| No new matches | Check active status, result cap, rule specificity, and whether relevant activity has been processed |
| Multiple content conditions never match | Required text must occur on the same added line |
| Excluded paths still appear | Use not contains inside an AND Match rule |
| Monitor creation is blocked | Check account-wide active capacity and use a workspace you own |
| No email for later matches | First-result email is a one-time notification |
| Search regex works but monitor regex differs | The features use different regex engines and case-sensitivity rules |
Troubleshoot Results
Section titled “Troubleshoot Results”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.
API errors
Section titled “API errors”The customer API has a separate error reference covering authentication, permissions, rate limits, and failures after a stream starts.
Get help
Section titled “Get help”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.