Troubleshooting
A practical checklist for the most common operational issues.
Triage Order
When something is not working as expected, verify in this order:
- Access and authentication
- Module permissions
- Input validity
- Network stability and retries
- Module-specific constraints
Access and Session Issues
Problem: "I cannot open a module"
Checklist:
- Confirm you are authenticated
- Confirm your account includes required access group
- Reopen the module after a fresh session
If Docs open but other modules do not, this usually indicates permission scope, not a platform outage.
Problem: "My session looks inconsistent"
Checklist:
- Refresh the page once
- Sign out and sign back in
- Reopen only one module first, then expand usage
Investments Issues
Problem: "Portfolio feels messy"
Checklist:
- Reduce bucket overlap
- Re-state each bucket intent in one sentence
- Remove inactive structures that no longer serve a thesis
Problem: "I rebalance too often"
Checklist:
- Define explicit rebalance conditions
- Add a minimum waiting period between structural changes
- Revisit latest report before reallocating
Budget Issues
Problem: "My month gets chaotic near closing"
Checklist:
- Update transactions throughout the month
- Keep pending vs. paid status current
- Run mini-reviews weekly instead of end-only reviews
Problem: "Categories are not helping decisions"
Checklist:
- Simplify category taxonomy
- Keep labels stable across months
- Separate insight-oriented categories from accounting noise
Reports Issues
Problem: "Report is stuck in processing"
Checklist:
- Wait and refresh after a short interval
- Verify network stability
- Retry only if processing state remains stale for an unusual period
Problem: "Report failed"
Checklist:
- Confirm the source request is still valid
- Re-run with clear and complete context
- Capture failure pattern if repeated
Assistant Issues
Problem: "Assistant asks me to enable Proa AI"
Checklist:
- Open Settings in the app
- Enable Proa AI
- Choose at least one data source: Budget, Investments, or Reports
- Retry with one concrete review question
Problem: "I reached my AI message limit"
Checklist:
- Open Billing to review AI message usage
- Wait for the next reset if you are on Free
- Upgrade only if you need more Assistant capacity
- Remember that report quota is separate from AI messages
Problem: "Assistant says a data source is unavailable"
Checklist:
- Confirm the source is enabled in Settings
- Confirm the module has current data
- Ask a narrower question about one module first
- Reopen the source module and verify the data directly
Problem: "A proposal expired"
Checklist:
- Ask Assistant to prepare a fresh proposal
- Review the new details before confirming
- Do not confirm proposals if the source data has changed unexpectedly
Problem: "Report creation from Assistant is unavailable"
Checklist:
- Check report quota in Billing
- Confirm Reports are available in your account
- Start from Reports directly if you need to inspect report status first
- Contact support if quota and access both look correct
Escalation Package
If you need support, provide:
- Module name
- Approximate timestamp (with timezone)
- What you expected vs. what happened
- Whether this is reproducible
- Any relevant identifiers (for example, report id)
This speeds up diagnosis and reduces back-and-forth.
For support requests, email contact@getproa.app.