Troubleshooting
Resolve import errors, stopped analyses, connection problems, and rejected reports.
Choose a symptom
| Problem | Next step |
|---|---|
| No installer or sign-in | Check release availability; account status. |
| Local app or model will not start | Development startup checks. |
| Data import fails | Check supported formats, size, and the selected sheet in Your data; check service authorization in Connectors. |
| Python cannot finish | Check the timeout, memory, file, and package restrictions in How code runs. |
| Export cannot replay | Check original large-file inputs and runtime requirements in Exports and replay. |
| Learning or display looks wrong | Check learning controls and Settings. |
Public installers are not available yet. The desktop implementation notes below describe the application source, not a supported public release. For current availability, see Download & install.
“is not a dataset” / unsupported file type
Check the extension against the supported list. SPSS .sav and .zsav, SAS .sas7bdat and .xpt, and Stata .dta are supported. Also check that a spreadsheet's first sheet is the table, not a cover page. A file with an unsupported or corrupt format is rejected. See Your data.
A run times out at 120 seconds
Smaller runs. Vectorize loops. Fit on a sample, then refit. For a large dataset, ask the agent to work with the file in place instead of loading it whole.
An answer was flagged for numbers
The number check found no source after two corrections. Ask the agent to compute and print the missing values, or drop the numbers. A flagged answer is unfinished. Do not quote it. See Evidence & literature.
A report was rejected
The rejection names the problems. Ungrounded numbers. A citation whose reference was never opened. A quote not found in the source. A missing table or figure. A language mismatch. The agent fixes them and resubmits. Supplied the references yourself? Open the sources first. Retrieval and opening are separate steps. Both are required.
“Web search is unavailable”
Literature search is temporarily down. Scholarly and package-documentation search still work. Only the general web search is affected, and a fallback answer is not a substitute for retrieved evidence. Retry the search or use an accessible source; do not describe an unretrieved source as verified.
“Session limit” / a turn is refused
The configured concurrency limit has been reached (eight running analyses by default). Wait for one to finish or stop it, then send your message again. The error reports the server capacity; a development operator can configure a different limit.
Disconnected, or Go does nothing
Plan approval cannot be sent while disconnected. The workspace says so instead of pretending. Reconnect (the turn survives a dropped connection) and press Go again. If a second window took over the session, use that window.
Nothing learned, or learning will not run
Learning needs a cue in your message or logged decisions, and both switches on. Check Settings → Research Conventions and Analysis Memory. See Memory & conventions.
Still stuck
In a desktop build, Settings → Data & System → Copy diagnostics copies a local diagnostic report, and App menu → Help → Open logs folder opens local logs. Review copied text before sharing it. These controls do not imply a public release or a support channel; see the product's download page for release status.