> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aefer.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> What to check when a request succeeded but meetings, recordings or webhooks are not what you expect.

Got an error code? See [Errors](https://docs.aefer.ai/api-reference/errors.md). Got a `200` but nothing happened? Check
here.

## What to check

| You see | Check |
| - | - |
| No meetings after connecting a calendar | The connection is `active`, not still `syncing` (`GET /calendar_connections?member_id=`), and the meetings start within the next 28 days. `active` with `last_synced_at` still `null` more than 30 minutes after `connected_at`, for a member whose meetings are recorded, means the first sync never finished: disconnect it (`DELETE /calendar_connections/{id}`) and send the member a new connect link. |
| A meeting the user expected isn't there | It is on the calendar they connected, under the account in `account_email`. |
| The same call listed twice | The workspace uses one calendar source: connected calendars or pushed events, not both. |
| "Won't record" on a meeting they want | `settings.sources["recording.enabled"]`: the assignment that decided, or a `reason` (`no_meeting_url`, `unsupported_platform`, `no_calendar_event`, `member_paused`…). |
| A bot `queued` long after `join_at` | `join_at` is the time you meant, with the right offset. |
| A bot `joining` for minutes | Someone in the call admits it: many calls hold guests in a waiting room. |
| Speakers unnamed | The meeting's participants carry emails; names improve as people recur. |
| Two bots in one call | The requests differed in `workspace_id`, link or `join_at`, or the first bot had already ended: a request returns the existing bot only while it is `queued`, `joining` or `in_call`. See [One bot per meeting](https://docs.aefer.ai/guides/send-bot.md#one-bot-per-meeting). |
| `processing` for hours | Contact support with the meeting id. |
| No webhooks arrive | The endpoint is in the meeting's workspace and names the event in `enabled_events`. Then find the event in [`GET /webhook_events`](https://docs.aefer.ai/api-reference/webhook-events/list-webhook-events): the answer your server gave, and [redeliver](https://docs.aefer.ai/api-reference/webhook-events/redeliver-a-webhook-event.md) it. |
| Webhooks fail verification | You sign the raw body, not re-serialized JSON, with the full secret including `whsec_`. |

## Contact support

Write to [support@aefer.ai](mailto:support@aefer.ai) with the workspace id,
the meeting, bot or connection id, what you expected and what you got, and when. Never send
your API key or webhook secret.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.