| Symptom | Likely cause | Fix |
|---|---|---|
| The AI answers generically, without referencing real LuxGov data | The tool/action was added but never actually connected to the AI's own "tool" or "action" slot | Delete the disconnected tool and re-add it through your platform's dedicated tool/action connection point, not a generic search-and-add |
| A request fails with an error mentioning an invented, wrong-looking URL | Your AI platform's "let the AI fill in this value automatically" feature has taken over an entire field, not just the one dynamic value it should have filled in | Find the field-level setting (often a small toggle or "defined automatically" label) and switch it back to manual/expression mode, then re-enter the correct value |
| Copilot Studio rejects your specification file on import | You're using the OpenAPI 3.0 file where Copilot Studio needs Swagger 2.0 | Use the Swagger 2.0 version specifically for Copilot Studio |
| An action or description looks cut off after import | A field exceeded your platform's own length limit | Shorten the description, or request a trimmed specification file from LuxGov support |
| ChatGPT's or Claude Desktop's built-in connector feature won't connect at all | Expected — see the AI Boundary Guide. Not a bug, no configuration fix exists today. | Use the Custom GPT path for ChatGPT, or a script/automation-tool path for anything else |
| Requests start failing after several quick questions in a row | You've hit your plan's rate limit | Wait a minute, then continue — expected behavior |
| A confident-sounding answer turns out wrong or made up | Your AI may not actually be calling the LuxGov tool for that question | Check your platform's tool-call trace/log to confirm the tool was actually invoked |
| "Are there any conflicts?" returns "not available" | This is not an error — conflict detection isn't built into this feature yet | No fix needed; this is the correct, honest answer |
| You can't find your key value again after generating it | Keys are shown only once, by design | Revoke the old key and generate a new one — there's no way to retrieve a lost key value |
Nothing here match your issue? Contact LuxGov support with your platform name and the exact error you're seeing.