Troubleshooting
Troubleshooting Flowlytics
Use this guide when the platform feels stuck, out of sync, missing data, or weaker than expected. The goal is to help you check the real source of the problem without jumping to outdated assumptions about how Flowlytics works.
Best use for this page
Quick triage when discovery is blocked, reports feel weak, or strategic views look stale.
What usually causes issues
Missing context, weak evidence, or a workflow reading from the wrong path rather than from the strongest project state.
What not to do
Do not try to bypass discovery or treat a completed method run as automatically good enough.
If discovery feels stuck
The most common reason is that Flowlytics still sees missing critical context. Discovery is designed to keep probing when answers are too broad or when the project foundation is still too thin to support the rest of the workflow.
- Answer more specifically instead of repeating broad phrasing.
- Upload supporting material if you already have briefs, notes, decks, or transcripts.
- If the project is incomplete, resume discovery instead of trying to work around it.
If reports feel weak
Method quality usually reflects one of two things: weak project grounding or weak external evidence. A report can complete successfully and still need a quality pass if the context or evidence behind it is too thin.
- Check whether discovery captured the product, objective, users, and constraints clearly.
- Check whether the right evidence exists for the method you are running.
- Review the output for specificity instead of assuming completion means quality.
If the report feels generic, the issue is often upstream. Strengthening the project foundation and evidence usually improves the result more than rerunning blindly.
If downstream views feel stale
Strategy, insights, and tracking surfaces should be reading from the canonical stored project state. When something looks out of date, the problem may be the read path rather than the project data itself.
- Refresh the view after major report completion or new evidence arrives.
- Check whether the project already has the analysis, records, or blocks that surface depends on.
- If a page still looks wrong, treat it as a workflow sync issue rather than assuming the project itself is empty.
Where to go next
Use these next guides if you need to improve the project foundation rather than just triage the symptoms.