Stopping, cut-offs and retries

Stopping

While the assistant answers, Stop is available and sending waits. After a stop the next step does not start. A step already under way finishes, and what the assistant managed to do stays done: the chat says "You stopped it. What the assistant managed to do is above, it stays done". An answer that was still being written when the person pressed Stop does not appear.

How a run can end without an answer

The chat shows the reason in plain words:

• The task took too many steps. The person says what to do next.
• The service the assistant runs on is not responding. Try again in a minute.
• Something broke on Talemo's side. Try again, and if it repeats, tell support the code shown.
• The answer broke off because it came out longer than one answer can be. Try again, or ask for less at once.
• There was too much data for one answer. Ask for less at a time, for example one day or one specialist. There is no Try again here: the same question would not fit again.
• AI is stopped: the balance is at the reserve, or the monthly spending limit is used up (see Spend of a run).

Trying again

Try again under a failure and Answer again under an answer run the same words as a new run. They are offered only on the last answer or failure, and only if the assistant changed nothing in it. After a change there is no way to repeat, so a booking or an edit is not made twice by accident.

When the server restarts

After a restart or a lost connection a run continues from the last finished step.

• A step that only reads is repeated.
• A step that changes records and was cut off halfway is not repeated. The step is marked "It isn't known whether this was done", and the person checks the record.
• A step that waits for approval stays waiting, and after the decision Talemo shows the action again and compares it with what was approved. If things changed in between, nothing is done: "Not done: things changed while it waited. Ask the assistant again."

When the online admin breaks off

The online admin has no person at the screen, so a run that ends without a reply to the client is passed to the team. The card says why:

• it took too many steps;
• it failed;
• the conversation was too long to read in one go;
• it hit its spending limit;
• it changed something and did not reply (check what it did);
• it could not reply.

A turn that ends in words with nothing sent to the client is retried once. After a second failure the chat is passed on as "could not reply". These handovers do not pause the online admin: it answers the next message from the client by itself, and the card asks a person to reply to this one.

A run that has already sent the client a message, or has passed the chat to the team itself, is not handed over again.