When a mate does not respond, check leave, startup, an active turn and model availability before restarting her.

Open the dashboard → Mate Settings → select the mate. Her controls are under Manage → Container.

On Today, “Not running. Go take a look.” calls for checking why she stopped. “On leave. Check in on her when you get a chance.” means an intentional pause.

First checks

What you see	Action	Expected result
Stopped and on leave	Use Wake Up when you want her to work again.	Wait for Running, then check a reply.
Stopped and not on leave	Check logs. If no maintenance is active, try Wake Up once.	She starts and stays running; record an error if she stops again.
Starting or just updated	Wait for the status to change.	Send after startup finishes.
Still on the previous turn	Check progress in that conversation and wait.	Send the next message after the turn ends.
An approval is waiting	Read Approve mate operations.	Decide after checking the scope; refuse anything you cannot see.
Restart loop	Select Pause in Manage, read and confirm the impact, then investigate.	The loop stops; the underlying issue still needs attention.

Running but not replying

Open Mate Settings → this mate → AI Model. Read the status and What to do. Use Model troubleshooting for credit, key or authorisation issues.
If dashboard replies work but the messaging app does not, check Message and notification problems.
Check that no important work or update is active. If a restart is needed, select Restart in Manage and confirm the mate. She goes offline briefly.
Wait for status to recover and send a short message to confirm a reply.

Still not working?

For continued silence, failed startup or another stop, check host resources and container logs, then contact support. Include the mate’s name, time, channel, model notice and redacted final log lines.

Handle a single mate’s issue at that scope. A whole-host restore replaces every mate’s later data and is not a routine step for missing replies.

unresponsive no reply stuck hung offline cannot start