# Bot Lifecycle

The bot will go through several lifecycle states when created, with different status marking when things went wrong.

### Standard Statuses

- `scheduled` - Bot is scheduled to join at a future time
- `booting` - Setting up the bot infrastructure and preparing to join
- `joining` - Attempting to join the meeting using the provided URL
- `recording` - Successfully joined and actively recording the meeting
- `processing` - Processing the recording after the meeting ends
- `transcribing` - Transcribing the audio using the selected model
- `finished` - Complete with transcript available for retrieval


### Failed Statuses

- `not_admitted` - Bot was not admitted to the meeting
- `bot_detected` - Google Meet, Microsoft Teams or Zoom detected the meeting bot as a virtual bot and blocked it. If this status is thrown then Skribby will automatically retry up to a maximum of 3 times.
- `auth_required` - Authentication was required but not provided to join the meeting
- `invalid_credentials` - Provided authentication credentials are invalid
- `failed` - An error occurred from our side, we've been alerted and will be looking into it. Feel free to reach out for more information.