Understanding results

Request lifecycle and partial results

How a request moves from pending to complete, and what you get if not every expert answers.

Statuses

status is pending, complete or failed. While the request is pending, responses holds every confirmed answer so far and the synthesis fields are null. A completed result doesn't change afterwards, except that follow_ups fills in when a follow-up round completes.

Timing

Most requests with 3–5 experts complete within 24 hours. That is a typical figure, not a service commitment. The eta is set at submission and updated as experts answer.

Deadlines and partial results

If not every expert has answered by your deadline, the request completes with the answers in hand: status: complete, partial: true, and experts_delivered lower than requested.
If no expert has answered by the deadline, the request fails with reason deadline_missed.
Without a deadline, Synquery keeps sourcing for a limited period, then completes with what it has.

Failed requests

A request experts can't answer returns status: failed with a reason such as deadline_missed or no_matching_experts. Failed requests are not charged.

Queueing

Rate limits govern calls, not panels. Submissions above expert capacity, or above your workspace's cap on open requests, are queued rather than rejected, and the eta reflects the queue.

Polling or webhooks

Poll Get status and answers, or receive webhooks. A response.received event fires for each confirmed expert answer.

Individual expert responses →

{ "request_id": "q_8f2k1x", "status": "pending", "experts_requested": 5, "experts_delivered": 2, "reused_answers": 1, "submitted_at": "2026-10-27T14:00:00Z", "eta": "2026-10-28T10:00:00Z", "last_received_at": "2026-10-27T15:10:00Z", "answer": null, "summary": null, "responses": ["…the 2 confirmed answers so far…"] }