Investigate a robot issue

Ask the agent about a robot issue in plain words. It finds the run, reads the logs, checks earlier runs, and answers with the evidence.

When to use it

• A robot failed and you want to know why.
• You want to know if it happened before, and on which robots.
• The answer needs more than one log, or a question to your most experienced engineer.

How to do it

1. Open the chat: type on Home, or click Alloy AI on the right edge of any page.
2. Name the robot and describe what you saw. A rough time helps but is not required.
3. Read the answer. Each finding links to the moment in Replay and the chart behind it.
4. Push back or go deeper: "check the other robots", "show me the IMU data at that moment".
5. Keep it: ask for a report to share, or a scenario to watch for it.

Example

Fictional example.

Ask: "QP-07 slipped on the stairs this morning. Why, and has it happened before?"

Agent: The slip is at 09:41:12: the front-left foot touched down 40 ms early on the step edge. The same early touch-down shows on 4 runs since release 5.3, all on QP-07 and QP-11. Likely cause: the 5.3 contact-detection change. Not confirmed: whether the step material matters. [Moment linked] [Chart] [4 runs]

Tips

• Describe the symptom, not your guess. If you have a guess, give it as one: "check whether it is the 5.3 change".
• Ask the history question. "Has any other robot done this?" turns one incident into a count.
• Connect Jira, GitHub and Grafana so the agent can check tickets, code and metrics too.

Related

• Root Cause Analysis
• Using the chat
• Getting good results