Reporting bugs — what to include so we can actually fix them
First: please do report bugs when you find them. A weird behavior you don't report is a bug that nobody else gets fixed either. MoonScanner is better because of user reports.
Second: the difference between a bug report that gets fixed in 24 hours and one that sits in limbo for a week usually comes down to how much detail was in the original post. This thread is a template for what to include.
The short version
Copy-paste this into a new bug report thread and fill it in:
**MoonScanner version:**
**Windows version:** (Win+R → type `winver` → enter)
**License tier:** Free / Pro / Elite
**What happened:**
**What you expected to happen:**
**Can you reproduce it?** (yes, every time / sometimes / once)
**Steps to reproduce:**
1.
2.
3.
**Logs attached?** yes / no
That alone gets us 80% of the way to a fix.
What tier you're on
Some scanners are Pro+ only. Confluence scoring is Pro+ only. AI features are Elite only. "The scanner isn't showing scores" is a bug if you're Pro; it's expected behavior if you're Free (you'll see a 🔒 in the Score column). Knowing your tier saves a back-and-forth round.
What happened vs. what you expected
These are two separate questions and both matter. "The scanner crashed" tells us something went wrong. "I opened the options flow scanner and clicked the RSI column header expecting it to sort, but the window froze for 10 seconds and then the app closed" tells us where something went wrong.
Reproducibility
- "Every time" — we can fix this fast. Deterministic bugs are the easiest.
- "Sometimes" — useful if you can identify the pattern (after the scanner has been running an hour? only during market hours? only on specific stocks?).
- "Once" — report it anyway, but expect a "let us know if it happens again" response until we can reproduce it.
Logs
MoonScanner writes log files while it runs. If you can include the most recent log with your bug report, debugging goes much faster. If you're not sure where to find them, just ask in your bug report and we'll walk you through it — log locations can vary slightly depending on how MoonScanner was installed.
If the bug is sensitive (your watchlist, account details, etc.) — message me directly instead of attaching publicly.
What NOT to report as bugs
A few things that look like bugs but aren't:
- "The scanner isn't finding any hits" — usually a slow market day or a narrow watchlist, not a bug. Check the Discord/IRC feed to see if the scanner is finding things in general.
- "Enrichment columns are empty" — short interest, RSI, MACD, squeeze metrics fill in after the initial scanner pass completes. Give it a minute.
- "AI Analysis isn't working" — requires Ollama or LM Studio running locally. Check the Elite setup guide.
- "Alerts stopped coming through" — could be market hours, could be your client disconnected from IRC/Discord. Verify the feed is live in the Kiwi web client or the Discord server before reporting.
- "Score and Signal columns show 🔒" — expected behavior on the Free tier. Confluence scoring is a Pro/Elite feature.
If any of those turn out to actually be bugs in specific cases, report them — but start by checking those common explanations first.
Where to post
- Bug Reports category — for anything you think is a real bug
- Support category — for "how do I do X" questions
- Feature Requests category — for things that aren't broken but could be better
If you're not sure which category, post in Support and we'll move it.
Thanks for helping make MoonScanner better.
— MoonBoss
