Skip to main content

Troubleshoot by symptom

Record the complete error and the action that produced it, then follow the checks below. Do not repeatedly overwrite files, switch targets, or restart equipment only to remove a message.

Startup and connection

SymptomCheck firstNext step
The desktop app does not reach App HubWhether the installation is complete and another Theseus process is already runningQuit completely and reopen; preserve startup logs if it still fails
The local Runtime target is unavailableThe current target and health state in system settingsSwitch back to the local target and check again; do not delete the app workspace
A remote target health check failsAddress, network, certificate, and RuntimeHost on the target machineFollow Connect a Runtime target one check at a time
Qixin is signed in but Run is unavailableWhether the current Runtime target is connected and authorizedQixin and target accounts are separate; use the connection prompt on the target row
A browser can open the target but management failsTrusted HTTPS and the current target-account roleProtected remote operations require the correct connection and Admin permission

AI problems

SymptomCheck firstNext step
No model is availableQixin sign-in or entitlement, Provider status, and model refresh resultOpen the AI Command Center guide
One Provider reports an errorThe authentication or network error on that rowRepair that Provider only; healthy Providers do not need to be removed
AI edits the wrong scopeWhether the request states the outcome, scope, constraints, and acceptance checksStop the task and ask for an impact list before the smallest repair
AI says it is done but the editor did not changeActual files, Problems, and the save/conflict state of the open tabTrust project assets and diagnostics, not the chat claim
A long conversation driftsWhether unrelated goals were mixed into the same taskStart a new conversation and attach only relevant files with @

Pages and runtime pages

SymptomCheck firstNext step
Runtime reports that no home page is configuredWhether the app has a homePageIdSet the correct page as home under Resources → Pages
The editor is correct but runtime shows older contentWhether the page is saved and whether Graph, PLC, or custom code also changedSave the page; rebuild resources that require Build/Run
A Page or Component does not openSchema, widget, method, or expression errors in ProblemsAttach the exact error and file with @; ask AI to diagnose before editing
A button does nothingWhether its action invokes an existing Page Method and diagnostics passCheck the property-panel binding and Problems; do not place scripts directly in action fields
A page asks for sign-inPage or widget role requirements and the current app userSign in with an app user, not a Runtime target account

Build, runtime, and Graph

SymptomCheck firstNext step
Build is unavailableWhether the app is Running, Debugging, Paused, or StoppingStop safely, then build again
Run or Debug failsThe first specific error in Console and ProblemsLocate the Page, Graph, PLC, or Script, repair it, and validate again
A Graph fails to buildWhether nodes, ports, object bindings, and variable references still existAsk AI to read current metadata and diagnostics instead of guessing fields
Debug does not stop at a breakpointWhether Debug was used and the breakpoint is saved in the current GraphSave the breakpoint and start Debug from Stopped
Saved logic does not change at runtimeWhether only the editor refreshed while the old instance remained activeStop, then Run or Debug again so the next instance loads the new assets

Devices, PLC, Pulsar, Vision, and Safety

SymptomCheck firstNext step
AI cannot understand an Axis, IO point, or cameraWhether Object Tree descriptions state physical and business meaningHave an engineer complete the semantics before AI orchestration
A device method is unavailableWhether the module is enabled, configuration is saved, and the app was reloadedSave while Stopped, then explicitly Run or Debug
PLC or a custom method does not appearWhether the latest app Build succeededRepair the build first, then inspect the callable list
Vision cannot generate or verify a versionCamera, inspection, samples, and an image-capable modelComplete each prerequisite; never substitute a fabricated OK result
Safety behavior is unexpectedInputs, outputs, groups, physical wiring, and safety hardwareStop equipment and involve a qualified engineer; do not let AI weaken interlocks

Data, import, and Git

SymptomCheck firstNext step
A value disappears after restartWhether a graph or app variable was used by mistakeUse Choose a data capability to select a saved variable, Recipe, or RecordStore
A Query failsURL, authentication, parameters, and the external responseTest a read-only request first; production writes require human approval
An imported ZIP cannot runHome page, module configuration, and assets that require a buildInspect it in the desktop app and run Build or Run
Git push failsCurrent branch, remote, credentials, and uncommitted changesFollow Collaborate with Git

When asking AI or support to continue

Provide at least:

  1. The exact action you were performing.
  2. The complete error, not only the last line.
  3. The current app state and Runtime target.
  4. The earliest relevant error in Problems or Console.
  5. @ references to the related Page, Graph, configuration, or Script.
  6. Which physical operations are stopped and which remain active.
warning

If equipment behaves unexpectedly, Safety state cannot be trusted, or on-site staff cannot confirm the risk, stop the equipment and follow the site's safety procedure. Do not continue experimenting online.