Check and Recover an AI Partner After a Problem

If an AI partner stops responding or a task fails, note which partner and step failed before opening Repair. A healthy status is a useful check, but the final proof is whether the original task works again.

Before you start

• Note the affected AI partner, task, and channel. Keep the latest failure message for comparison.
• Pause repeated submissions of an important task so it is not run twice while you troubleshoot.

1. Open the right repair flow

In AI Partner Management, open Repair and select the affected runtime platform. Check the name at the top of the page before running a repair.

2. Run the quick repair

Start the quick repair and wait for it to finish. The page shows stages for preparing the environment, checking status, confirming the AI partner, and confirming the result. If a stage does not finish, read its message. Open Technical Details when you need more information.

The quick repair handles common recoverable issues. The page says this flow does not delete AI partners, skills, or chat data.

3. Check the current status again

Select Check Again and wait for a fresh result. The Healthy state in the image means the current check passed; it does not prove that your original issue is gone.

4. Verify with the original task

Return to the task or channel that failed and retry the smallest useful part. Check that the partner responds, the task finishes, and the result is usable. Only then return to Repair and select Fixed.

If the issue remains, select Not Yet and follow the next step shown on the page. If the quick repair failed or stopped, inspect the error details before deciding whether to continue with the deeper repair.

Done when

The fresh check passes and the original task completes again. Review any output that still needs your decision. Treat the issue as resolved only after both checks pass.

Troubleshooting

• Healthy status, but the task still fails: confirm that you selected the right platform and partner, retry the original task, then choose Not Yet if it still fails.
• Quick repair did not finish: read the failed stage and Technical Details, then retry or continue with the deeper repair as prompted.
• Deeper repair finished, but the outcome is unclear: refresh the status as prompted and verify with the original task.

Related pages

If you have not claimed a partner yet, start with Quickstart in Docs. For partner roles and runtime status, see AI Partner Workspace.

Data boundary

Work data stays on your device by default; only channels you connect and model calls go online as the task requires.