N3squik
01/09/2026, 8:59 AMChiranjeet Mishra
01/11/2026, 1:08 PMassistant object) and any custom assistant overrides
While you provide that, try these quick checks that resolve most stuck/no-response runs:
1. Confirm run endedReason
• GET /eval/run/{runId} and inspect endedReason. If not mockConversation.done, note the value (e.g., assistant-error, pipeline-error-*, timeout).
2. Verify assistant health
• Manually chat with the assistant in the Dashboard to confirm it responds.
• If it fails manually, check assistant model/provider credentials and tool endpoints.
3. Check tool endpoints and timeouts
• If the assistant calls tools, ensure tool endpoints are reachable and returning within expected time (tool failures often cause runs to hang).
4. Re-run with simplified target
• Run the eval against a transient assistant with minimal config or against a different assistant to isolate whether problem is eval or assistant.
5. If using AI judge/provider overrides
• Verify provider credentials (OpenAI/Anthropic/Google) and model names; provider errors can block completion.
Share the eval ID + assistant ID or paste the GET /eval/run/{runId} JSON (especially endedReason and results) and I’ll investigate further.N3squik
01/11/2026, 2:16 PMChiranjeet Mishra
01/13/2026, 9:58 PM