Troubleshooting
An empty feed, scores you disagree with, alerts that did not arrive, and how to tell a configuration problem from a quiet week.
The feed is empty
Almost always one of three things, in this order of likelihood:
- The score floor is too high for how specific your terms are. Lower it in steps of ten rather than all at once.
- The terms are too narrow. An exact phrase term matches far less than people expect. Try the same words as include terms first.
- It is a quiet week. A niche that produces four good conversations a week produces none in some weeks. Judge over a fortnight, not a day.
An empty feed is a legitimate outcome. The product is built to surface few things, and a tool that always has something for you is not scoring anything.
A score looks wrong
Open the breakdown before changing anything. Most surprising totals come from one factor, and the fix depends on which:
- Relevance low, everything else high — the conversation is about a neighbouring problem. Usually an exclude term.
- Purchase intent low on an otherwise perfect thread — the person is describing the problem, not shopping. That is working correctly, and those threads are often still worth a reply.
- Freshness dragging a strong lead down — an old thread with real intent. Worth reading; rarely worth replying to.
An alert did not arrive
Check the email score floor on the workspace first — it is separate from the feed's floor, and a lead can be in your feed while sitting below the threshold that would have mailed you.
Empty digests are suppressed deliberately, so a quiet period produces silence rather than a mail saying nothing happened.
Something is wrong with the service
/api/healthcheck reports whether the application can reach its database. It answers with a 200 and {"services":{"database":true}} when healthy, and a 503 when not.