Troubleshooting

Most disturbances can be assigned to a group of causes within a few minutes. This page shows where to look for that. The detailed troubleshooting is in the operations manual that comes with the delivery package.

Where do I look first

1. Admin panel, page Logs. It shows the individual requests with model, duration and cost, the same requests summarised per conversation, the errors from the Outlook add-in and the server logs. See Logs and audit.
2. The Access page of the person concerned. For the question why someone does not see a connector, this is the fastest answer: it names the decisive rule level per connector.
3. Only then the server level. What does not become visible in the panel are disturbances that already occur when the application starts.

The most common groups of causes

Picture	Where the cause usually sits
Answers do not arrive or run into timeouts	The instance does not reach the internet: typically a VPN client, a corporate proxy or a colliding network route. Less often an invalid key of the inference provider.
A feature is visible but does nothing	The corresponding optional part is not running or is not configured. Affects mainly file search, code execution and web search.
A service restarts repeatedly after the installation	Access permissions on the storage areas of the instance. On the regular setup path this does not occur.
Answers appear only at the end in one go	An upstream appliance buffers the response stream, see Domain and certificate.
After a migration every person has to reconnect their connectors	The encryption keys were regenerated instead of carried over, see Backup and migration.
After an update something in the interface no longer fits	The configuration no longer matches the current state, or a new value is missing from it.

If none of this fits

Note down what was changed last and compare your configuration with the supplied template. A large part of the remaining disturbances comes down to a missing value or to a configuration that no longer matches the current state after an update. If that does not get you further, the support path from your contract does.

Next

ConfigurationWhich level wins and where each setting is maintained.

Backup and migrationBack up, restore and move to a new server.