Common errors

Overview

Most errors people report in GrowthOS fall into a small number of buckets: a permission problem (wrong role or seat), a stale session, an AI generation failure, or an MVP feature boundary being mistaken for a bug. This page walks through the fastest way to tell them apart.

A genuinely broken feature is rare compared to these four causes, so working through this checklist before filing a bug report saves everyone time and usually resolves the issue immediately.

If none of the common causes match, the fastest path to a real fix is a support message that includes what you were doing, what you expected, and what actually happened, ideally with a screenshot.

What you can do here

Diagnose a permission-denied error by checking your role and seat type.
Resolve a “stuck loading” or stale-data issue by refreshing or checking Sessions.
Tell an AI generation failure apart from a genuine bug.
Recognize a coming-soon message as expected MVP behavior, not an error.
Write a support message that gets a fast, useful response.

When to use

Something in the app looks broken and you are not sure why yet.
You see an error message you do not recognize.
Before filing a support ticket, to rule out the common causes first.

Prerequisites

A signed-in member account.

Where to find it

Getting Started / Troubleshooting → Common errors, in the docs sidebar.

Step-by-step

Note the exact error message or behavior, and where it happened.
Check whether it is a permission issue: confirm your role and seat type on Members.
Check whether it is a session issue: refresh the page, or check Sessions for a stale login.
Check whether it is an AI generation failure: retry once, since AI calls occasionally time out.
Check whether it is actually a coming-soon message for a feature outside MVP scope.
If none of the above match, message support with what you were doing, what you expected, and a screenshot.

What success looks like

Most issues resolve from this checklist alone, without needing to contact support.
When you do contact support, the message already rules out the common causes, speeding up the fix.
You can tell the difference between a bug and expected MVP behavior.

Tips & best practices

Try refreshing before assuming something is broken; a surprising number of “bugs” are stale page state.
Retry an AI generation once before reporting it as failed; occasional timeouts are normal.
Include a screenshot with any support message; it cuts back-and-forth significantly.

Common mistakes

Filing a bug report for a coming-soon message instead of recognizing it as expected MVP behavior.
Assuming a permission error is a bug instead of checking role and seat type first.
Reporting an issue without enough detail for support to reproduce it quickly.