Troubleshooting
Common setup, auth, sync, and experiment issues.
Use oriyn status first, then fix auth, product linkage, data freshness, missing personas, or hypothesis quality based on the failing check.
Run Status First
oriyn statusoriyn status checks auth, API reachability, linked product resolution, and local configuration. Start there before debugging a failed experiment.
Common Issues
| Symptom | What to check |
|---|---|
| Not logged in | Run oriyn auth login or set ORIYN_ACCESS_TOKEN in CI. |
| No linked product | Run oriyn link from the repo and commit oriyn.json. |
| No personas | Connect data, run oriyn sync, then inspect integration status. |
| Thin or generic results | Write a narrower hypothesis and confirm source data covers the changed workflow. |
| Network or API error | Retry after oriyn status; if it persists, contact shivam@oriyn.ai with the command and timestamp. |
Report A Problem
For beta support, include the CLI version, command, product id if safe to share, timestamp, and whether the issue happened in the web app, CLI, CI, or an agent environment.
oriyn --version
oriyn status