Waiting for decision
What happens to a message that waits for a human, hold reasons, approving a reply and approving a tool call.
"Waiting for decision" is the team page where the operator makes decisions. Messages the bot answered by itself do not get here: a ticket appears only when a human is needed.
1. What happens to a message
- The message goes into a conversation: the conversation key is the channel and the chat; a conversation closes after it has been quiet for more than 4 hours (the setting
conversationIdleHours). - Two layers assess the risk: rules (L1) and a classifier (L2) (Triage and risk engine).
- The team's lead decides: answer itself, hand it to an executor, or call a human; the executor or the lead prepares the reply.
- The reply goes through checks before it is sent.
- No reason to hold — the reply goes to the channel and there is no ticket; the conversation is visible on the "Conversations" page. A reason exists — a ticket with the status
waiting_operatoris created, and the person gets in the channel:Запрос принят и передан оператору на проверку. Ответим в течение нескольких минут.(the request is accepted and passed to an operator for review; the server writes it in Russian).
While a ticket waits, new messages of that conversation go into the same ticket.
2. Hold reasons
The reason is shown by the "What checked it" block in the ticket and by the holdReason field:
| What is written | What it means | What to do |
|---|---|---|
Контур команды: … (team contour) | the agent's model is external, and the team's contour is closed | cradle teams update <slug> --contour cloud or a local model (Keys and models) |
| "The reply check failed, so the auto-reply was held" | the draft check failed ("Citations", "Reply hygiene"); details are in the "Reply checks" block | fix the text; you can also send despite the failure — the decision goes to the audit log |
Уровень риска yellow (или red) — требуется решение оператора. (risk level — an operator decision is needed) | rules or the classifier fired | decide; rules are set on the team's "Triage & Risk" tab (an overview is on the "Security" page) |
Классификатор рисков (L2) не отработал, вердикт опущен до L1 … (the L2 classifier did not run, the verdict fell back to L1) | the cradle has no model for the classifier or it returned an error | Keys and models |
Черновик не подтверждён источниками (strict grounding) — отправка задержана. (the draft is not backed by sources) | the agent is in Strict mode and the reply has no backing | check the knowledge base (Knowledge bases) or answer by hand |
Агент не сформировал черновик ответа. (the agent did not produce a draft) | the agent has no model or it did not answer | the agent's model; answer by hand |
lead_escalation | the lead chose "needs a human" | answer by hand |
tool_approval | a tool call waits for approval | section 4 |
task_ci_failed | the external executor's PR is red even after the return | External code agent |
3. Resolve a ticket
In the console: the team page → Waiting for decision (the number of waiting tickets is next to it). The buttons "Pending", "Rejected", "All" and the selects "All risk", "All channels", "All leads" narrow the list. Open a ticket: on the left the message and the path through the team, on the right the "What checked it" block (layer 1 — rules, layer 2 — classifier, result), "Reply checks" and the reply field.
| Button | What it does |
|---|---|
| Approve & send | sends the agent's draft as it is |
| Edit & send | appears when you changed the text: sends your version |
| Send reply | when there is no draft: sends the reply you wrote by hand |
| Reassign | another agent regenerates the draft (the window "Переназначить агента" — reassign the agent) |
| Reject | the window "Отклонить тикет" (reject the ticket) with an optional reason: nothing goes to the channel, the status is rejected |
The Conversation button opens the whole conversation. The operator's answer goes to the same channel and is written into the conversation as an operator message.
Listing and viewing tickets are commands:
cradle tickets list --status waiting_operator
cradle tickets show <ticket-id>The commands cradle tickets approve and cradle tickets reject answer
not implemented in version 0.9.2. The --status filter takes an exact status:
waiting_operator, approved_sent, rejected, error.
How to check. The ticket left "Pending", the counter went down, the status is
approved_sent; the reply arrived in the channel.
If it did not work.
- The status
error— sending to the channel failed (for example, it is stopped): turn the channel on (Channels) and press Approve & send again. - "ticket already handled" — another operator has already resolved the ticket.
4. Approving a tool call
A ticket with the reason tool_approval is created when an agent wants to call an
irreversible tool or an external code agent (code.dispatch; every such run waits
for a human). It has no draft. Approval grants the permission for the call on your
behalf and continues the executor's task; rejection ends the task with an error and
nothing is started.
In the console these are the same buttons on the ticket page. The ticket shows the original message but not the call's arguments.
In the 0.9.2 console the Send reply button of such a ticket is active only
when the reply field has some text: there is no draft, and the field is empty.
Type any text into it and press the button — for tool_approval the server does
not use the text, it grants the approval. Reject works without text.
How to check. The task status in the conversation changed: the executor started
work (for an external agent — the message Задача отправлена исполнителю … (the task was sent to the executor)).
If it did not work. The message Не получилось: … (it did not work) in the conversation names the reason — for example, GitHub rejected the
workflow run (External code agent).
5. Conversations
The Conversations page shows everything said to the team's bots: the filters "All", "Open", "Closed", channels, a search by text. A conversation has a "Transcript", a "Summary" (it appears after closing), "Tasks" and "Tickets". A conversation has a ticket only if a human was needed: "No tickets: the bot answered everything itself".
How to check. Your test message is found by the search by text.
If it did not work. "No conversations yet" — the message did not reach the channel or went to another team (Channels).
Channels
How to turn on and check the HTTP API, Telegram (bot and groups), the widget and the incoming MCP channel, and which team a message goes to.
External code agent
How to connect an executor that works in GitHub Actions and opens a pull request — the workflow, secrets, the list of repositories, the token, the manifest, running, approval and typical failures.