2 Check Status

Step 2: Check Status

Poll the task summary until overall_status is completed. Because metrics were included at upload, the task automatically progresses through validation and metric processing without any additional requests.

What this step does

It reads the task's rolled-up progress via GET /ingestions/:id/summary, using the data.id captured in Step 1. The summary reports overall_status and per-row by_status counts, letting you watch the task move from pending through to completed and drive a progress bar without pulling the full entity list each time.

Why it's needed

Ingestion and metric processing are asynchronous โ€” Step 1 returns as soon as the task is accepted, long before geocoding, matching, and metric computation finish. There is no synchronous "done" signal; the only way to know results are ready is to poll this summary until overall_status reaches completed. Fetching results (Step 3) before then would return partial or empty metric data. The summary endpoint exists precisely so you can poll cheaply โ€” status counts only โ€” rather than repeatedly downloading every row.

Why you poll until completed (not staged)

In the full ingestion workflow you poll only until staged, then trigger metric processing yourself. Here, because metrics were requested at upload, there is no manual trigger and no intermediate stop โ€” the task runs all the way through on its own. So the terminal state you wait for is completed, the point at which every requested metric has finished computing.

Request

GET /ingestions/:id/summary

Task Status Progression

pending โ†’ staging โ†’ staged โ†’ processing โ†’ completed

Unlike the full workflow where you poll until staged and then trigger processing separately, here you poll until completed in one go.

Frontend Usage

  • Progress bar: Use by_status to show overall progress
    • Progress % = completed / total ร— 100
  • Status badge: Show overall_status
  • Poll interval: Every 5โ€“10 seconds until overall_status === "completed"
  • Confidence breakdown: Show high/medium/low counts once available

Next Step (when completed)

โ†’ Step 3: Get Results (GET /ingestions/assets/:id)