Skip to content

Common errors

Most errors fall into a few buckets: a permission problem (wrong role or seat), a stale session, an AI generation failure, an MCP key or agent-claim issue, or a coming-soon module being mistaken for a bug.

Work through this checklist before filing a bug. If none match, message support with what you were doing, what you expected, and a screenshot.

  • 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 for modules not in the current product.
  • Fix a gos_ key or agent-claim problem (expired key, confirm-before-claim skipped).
  • 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.
  • A signed-in member account.
  • Getting Started / Troubleshooting → Common errors, in the docs sidebar.
  1. Note the exact error message or behavior, and where it happened.
  2. Check whether it is a permission issue: confirm your role and seat type on Members.
  3. Check whether it is a session issue: refresh the page, or check Sessions for a stale login.
  4. Check whether it is an AI generation failure: retry once, since AI calls occasionally time out.
  5. Check whether it is actually a coming-soon message for a module not in the current product.
  6. If an agent failed: confirm the gos_ key is valid, MCP URL is correct, and you confirmed the claim.
  7. If none of the above match, message support with what you were doing, what you expected, and a screenshot.
  • 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 a coming-soon module.
  • 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.
  • Filing a bug report for a coming-soon message instead of staying on Idea Lab, UX Spec, and sprints.
  • 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.