An answer is missing, weak or out of date
Check that you are in the intended Mind and using your own account. Ask the agent to show the sources it could use, then open the relevant record. An excluded or missing result is not permission to infer its contents. Recovering from a poor answer explains the source and scope checks.
If the saved record is wrong, propose a correction. If an earlier version is being treated as current, inspect current information and evidence before replacing anything.
A change is waiting or was refused
Read the actual result. Held means the proposal is waiting; applied means it saved. Review rules explain why eligible changes can have different outcomes. Reviewing the request explains the next step.
For a refusal, identify the account, area and action. An authorised owner or admin can inspect effective access. Do not use a different identity or copy protected material into another area to get around the boundary.
Sign-in or the connection stopped working
Follow sign-in and reconnection. Separate the Mensara account, the Mind’s Portal, an external AI client and a model-provider connection. Success in one does not establish the others are connected.
If a response was lost during a write, review, invitation or payment, inspect the original work before submitting it again.
A sensor, agent or loop is not producing useful work
Check what is actually installed and enabled. Then inspect the schedule, run or case, connections, access and budget. Use capture checks, agent lifecycle, or loop cases for the relevant job.
An entry in a catalog, a composed loop or a successful installation is not a completed run. Inspect the output and any waiting review before relying on it.
Backup or a bill needs attention
For missing or stale backups, follow backup and recovery. Keep the Recovery Kit and keys out of support messages. For account plan or payment state, use account and billing; for model usage, use usage and costs.
Give support a useful report
Include what you tried, what you expected, the actual message, the time, the relevant app or request reference, your role and the installed version. State whether a harmless read still works and whether the failure is repeatable. Use a disposable example when demonstrating the problem.
Do not include private keys, tokens, recovery material, payment-card details or customer document bodies. Keep the original work reference so the operator can distinguish a failed action from a lost response.
Related
Practical guides for people and agents