The bot will go through several lifecycle states when created, with different status marking when things went wrong.
scheduled- Bot is scheduled to join at a future timebooting- Setting up the bot infrastructure and preparing to joinjoining- Attempting to join the meeting using the provided URLrecording- Successfully joined and actively recording the meetingprocessing- Processing the recording after the meeting endstranscribing- Transcribing the audio using the selected modelfinished- Complete with transcript available for retrieval
not_admitted- Bot was not admitted to the meetingbot_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 meetinginvalid_credentials- Provided authentication credentials are invalidfailed- An error occurred from our side, we've been alerted and will be looking into it. Feel free to reach out for more information.