3 Poll Task Status

Poll the task status until it reaches a terminal state. For async searches (file uploads or >500 points), you need to poll this endpoint until status is completed, completed_with_errors, or failed.

For sync searches (โ‰ค500 JSON points), the task is already completed when the search returns.

When complete, links.results and links.summary will be included in the response.

What this step does

It re-reads the parcel_search_task and reports how far the background search has progressed. While the lookup is still running the task sits in pending or processing; once it finishes it flips to a terminal overall_status and the links.results / links.summary pointers appear. The after-response script records {{parcel_task_completed}} so a runner can decide whether to keep polling.

Why it's needed

The results and summary endpoints have nothing to return until the search has finished โ€” asking for them mid-flight is premature (the summary returns 409 while incomplete, see Step 4). This step is the gate: it confirms the parcels have actually been resolved before the downstream review and ingest steps run. It also distinguishes completed_with_errors (some points failed) and failed (the whole task failed) from a clean completed, so you learn how it ended rather than assuming success.

When you can skip it

You only need this poll for asynchronous searches โ€” file uploads (Step 2) or JSON bodies over 500 points, which return 202 and finish in the background. A small synchronous JSON search (Step 1, โ‰ค500 points) is already terminal when it returns, so you can go straight to the summary or results without polling.

Next Step

โ†’ Step 4: Get Task Summary (GET /cadastral/tasks/:id/summary)