Core troubleshooting and browser data
Applies to: Public Core prototype
Updated
Begin by recording the page URL, selected object and visible error. A loading problem, a navigation problem and an unavailable connection require different checks.
Loading and navigation#
| Symptom | What to try |
|---|---|
| Core does not finish loading | Confirm the connection, allow required page scripts and retry in a current browser. Record any error that remains. |
| The rendered view is blank | Check whether browser graphics acceleration or a graphics capability is unavailable. Try another current browser before changing system settings. |
| A control appears unresponsive | Close any open dialog, move focus out of a text field and retry the labeled control. |
| An object is difficult to find | Open Explore and use Find a page. Confirm the selected collection. |
| Next or Previous is disabled | You may be at the boundary of the current collection. Use Explore to select another destination. |
| A page is absent from the collection | Use its original website URL or search Product Documentation on the company site. |
For long technical material, Open original page provides the conventional reading surface. The Product Documentation hub is also available independently of Core's rendered interface.
Messages and external operations#
If a message remains queued or fails, read the connection indicator and the error before resubmitting. A disconnected model cannot provide a response simply because the composer is available. Preserve text you need while diagnosing the connection.
If a product action appears successful but you expected a change in another application, check which environment you are using and inspect that application's result. The public prototype includes representative interfaces and local operations. It is not a general connection to your accounts or equipment.
Browser data#
Conversation state and saved business briefs can remain on the current device when browser storage is available. They do not automatically follow you to another browser or computer. Temporary browsing sessions, storage restrictions and clearing site data can remove them.
Use Clear saved brief to remove the brief through its own form. Before clearing broader site data, preserve any information you need. Clearing site data is a local reset; it does not recall messages already submitted or reverse an operation performed by a connected application.
Report a reproducible issue#
Contact support@valen-systems.com with the URL, browser and operating-system versions, viewport or device type, selected object, action taken and resulting behavior. State whether the issue persists after a refresh and whether browser storage is restricted.
Include a short redacted error or screenshot if it helps identify the control. Do not include credentials, private messages or customer records. A report that names the exact object and action is more useful than a general statement that the interface failed.