Bot statuses
Every status a bot can be in, what it means, and what to do.
Every bot has a status that tells you whether it's chat-ready and what action to take next. The status is shown as a colored dot with a label on bot cards and at the top of the bot detail page.
Status reference#
| Status | What it means | What to do |
|---|---|---|
| NO_DATA | The bot exists but has no documents yet | Upload documents |
| UNTRAINED | Documents are uploaded but the bot has never been trained | Train the bot |
| PENDING | A training job is currently running | Wait — watch the queue position / phase indicator |
| READY | The bot is fully trained and ready to chat | Open Chat Workspace and start a conversation |
| OUTDATED | Documents changed since the last training; the bot is still chatable but uses old context | Retrain when convenient |
Transition diagram#
NO_DATA → (upload) → UNTRAINED
UNTRAINED → (train) → PENDING → READY
READY → (change documents) → OUTDATED
OUTDATED → (retrain) → PENDING → READY
PENDING → (training fails) → UNTRAINEDWhat "OUTDATED" really means#
When you upload a new document or delete an existing one after a successful training, the bot's manifest changes. The current trained version no longer reflects the latest documents. Pegasus marks the bot OUTDATED but does not break chat — old context is still better than nothing.
When you retrain, only the delta (added/removed files) is re-processed, so subsequent trainings are usually faster than the first.
Chatting against a non-READY bot#
| Status | Can you chat? |
|---|---|
| NO_DATA | No — the bot has no knowledge |
| UNTRAINED | No — never trained |
| PENDING | No — training in progress |
| READY | Yes |
| OUTDATED | Yes — but answers may not reflect recent document changes |
If you try to chat with a bot that isn't ready, Pegasus shows the message "Bot is not ready for chat." See Bot is not ready for resolution.