Troubleshooting

Common problems with joining, speakers, calendars and providers, and what to do.

The meeting status shows the reason a join or a job failed. Start there.

The bot waits and never joins

  • Google Meet: the host or a participant has to admit the bot from the lobby. Admit Minutd Notetaker when it asks.
  • The lobby timeout passed. The default is 10 minutes. Raise it in Settings, Bot.

The bot cannot join a Teams meeting

The tenant that owns the meeting must allow anonymous users to join. A Teams administrator controls this in the meeting settings and the meeting policy. If it is off, the status says “This tenant blocks anonymous guests” and Minutd cannot work around it. Ask the organiser or use a meeting from a tenant that allows it. See Microsoft Teams for the other join failures.

Some meetings are skipped

Check the join rule for that calendar. The rule may be set to only meetings you organise, or only with external guests.

Speakers are wrong or missing

Minutd reads speakers from the Meet and Teams pages. Those pages change often, and a change can break the reading until the selectors are updated. Transcripts still work, just without names. If you see it, open an issue with the platform and date, and update to the newest version. Provider diarization can be turned on as a fallback.

Google sign-in fails

  • redirect_uri_mismatch: the redirect URI in the Google console must match the one shown under Settings, Accounts, character for character. It ends in /api/oauth/google/callback. Behind a reverse proxy, set MINUTD_PUBLIC_URL.
  • Calendar access stops after a week: your consent screen is in Testing. Set it to In production. See the Google guide.

Microsoft sign-in fails

  • AADSTS50011: the redirect URI does not match. Copy it again from Settings, Accounts. It ends in /api/oauth/microsoft/callback. Behind a reverse proxy, set MINUTD_PUBLIC_URL.
  • Calendar sync stopped months after setup: the client secret has expired. Create a new one. See the Azure guide.

Transcription or summary fails

Press Test next to the provider in Settings. Wrong keys, missing models and unreachable base URLs show up there. For the local provider, check that the whisper service is running (docker compose --profile local up -d). A failed transcription shows its error on the meeting page, and Re-run transcription tries again.

The server runs out of memory

Lower the concurrency cap. See sizing.

A supporter key is rejected

Copy it again without spaces or line breaks. Keys are checked offline, so a rejection is about the key text, not your network.

Edit this page on GitHub