# FAQ

## The first migration hangs or takes very long

On first start, the `vector` extension builds its indexes — this can take a few minutes.
Check the logs with `docker compose logs -f web`. If the migration fails with a `vector`
extension error, it is not enabled in the database.

## The AI features don't respond

Make sure a valid [AI key](https://lalabase.com/docs/en/self-hosting/configuration/ai-byok) is set and the instance has
**outbound** access to the provider. The worker logs show whether requests are failing.

## Emails are not being sent

Check the [SMTP configuration](https://lalabase.com/docs/en/self-hosting/configuration/environment) and whether the
[worker process](https://lalabase.com/docs/en/self-hosting/operation/background-jobs) is running — emails are sent as a
background job.

## Something behaves oddly after an update

Was the [worker restarted](https://lalabase.com/docs/en/self-hosting/operation/updates)? If it runs old code, its logic no
longer matches the migrated database. Restarting the worker service fixes this.

<div class="docs-callout docs-callout--info">
  <div class="docs-callout__title">Nothing found?</div>
  <p>Describe your problem with the relevant log excerpts in the public repository — that way other self-hosters can help.</p>
</div>