If you receive a "Bot unavailable for SDK" message when sending a /start-mission request, this is most commonly caused by an incorrect bot_slug or a MISSION_SLUG conflict in your .env file.
Before You Start
Make sure you have your SDK Access Token ready. This is required to use the SDK.
If you haven't set it up yet, check out our guide on how to find your SDK Access Token before proceeding.
Cause 1: Incorrect Bot_Slug Format
Your bot slug must follow the correct format.
Three words separated by hyphens, all in lowercase.
For Example:
Bot ID: Oring Mass Node
❌ Incorrect: Oring Mass Node
✅ Correct: oring-mass-node
Format:
bot_slug = oring-mass-node
How to fix:
Open your .env file and update and use the correct BOT_SLUG value
Save the file and restart the server
Cause 2: MISSION_SLUG Conflict
If your .env file contains a MISSION_SLUG variable, this can also trigger the "Bot unavailable" error.
How to fix:
Open your
.envfileRemove or delete the
MISSION_SLUGline entirelySave the file and restart the server
Note: You can always control your rover without MISSION_SLUG as it is only required for dry runs and competitions.
Still having issues?
If the error persists after trying both fixes above, please open a support ticket on Discord or reach out to us via e-mail at hello@frodobots.com and include your bot slug and any error logs from your terminal.