What this helps with
Use this section to check why Flowlytics may feel stuck, incomplete, or out of sync, and what to review before rerunning work.
If discovery feels stuck
Discovery can pause when Flowlytics still needs important project context before it can move forward.
- Add more specific detail instead of repeating broad or general answers.
- Upload supporting material if it helps explain the project, audience, product, or problem.
- If the project setup is not complete, return to discovery and continue from where you left off.
If reports feel weak
Report quality depends on the project context, uploaded evidence, and the information available when the method runs.
- Check whether discovery explains the project clearly enough.
- Review whether the method has enough relevant evidence to work from.
- If the report completes but feels too generic, improve the context or evidence before running it again.
If downstream views feel stale
Some views depend on saved project data, completed reports, analysis blocks, or records that may not be available yet.
- Refresh the view after completing major reports or updates.
- Check whether the project has the analysis, records, or blocks needed for that view.
- If something still looks wrong, review the source project data before assuming the output is missing.