/REFERENCE & LIMITS
Troubleshooting
A quick table of the problems people hit most often, and the first thing to check for each one.
EveryoneMost problems trace back to one of a few causes: the knowledge isn’t loaded, you’re looking at the wrong project, or a single source can’t be read. Find your symptom below and start with the suggested check.
Common issues and fixes
| Symptom | What to check |
|---|---|
| A thin answer, or Edmund says it doesn’t have that | The knowledge isn’t loaded, or you’re in the wrong project. Confirm you’re in the project for that machine, then add the missing documents or data. See Your first answer and Documents. |
| A document shows No text | It’s a scanned or image-only PDF with no text layer. OCR it or re-export with a real text layer, then upload that version. See Documents. |
| You can’t see a project that should be there | It’s a question of role and team visibility, not a fault. Ask an administrator to give you access. See Users, roles & teams and Roles & permissions. |
| A data source returns nothing, or errors | Check the read-only database user and the connection details. See Data sources & SQL safety. |
| A PLC program won’t index | PLC support is alpha. Check the export you uploaded; that’s the usual cause. |
| Voice or attachments aren’t working | This is usually connectivity at the machine. Move to a spot with a better signal and try again. |
Tip
When an answer looks wrong or empty, confirm the project before anything else. A correct question asked in the wrong project will always read as missing knowledge.
If a problem persists after the check above, it may be a known limit rather than a fault. The cornerstone pages linked in each row go into more detail, and the documentation overview lists everything else.
