get_run

md.mostlyright/datasets · Verify this server

One run's current state: status, mode, the clamps it ran under, rows delivered and whether a clamp truncated them, how many pages a many-page source reached, the table and table version it sealed, the failure code, detail and stage when it failed, and the version number a confirm or cancel should send. Example: {"run_id": "…"}. Returns {run_id, status, mode, clamps, rows, bytes, truncated, covered_window, table_id, table_version_id, outcome, failure, created_at, completed_at, version, dashboard_url}. rows, bytes, truncated, covered_window, clamps and table_version_id are null until the run has delivered them — a queued run states none of them, and a succeeded refresh whose sources were unchanged has outcome "unchanged" and seals no table version. ALWAYS read truncated before treating a sample as complete: a clamped sample succeeds. A run over a source that gathers many pages also returns pages {discovered, discovery_requests, discovery_complete, duplicates_dropped, known, fetched_this_run, unchanged, changed, failed_this_run, pending, failed, skipped, budget_exhausted, complete}, and it is absent on every run that gathered none. pages.complete false is NOT a failure: the run succeeded with explicit partial coverage, budget_exhausted names the ceiling it stopped at, and the next refresh continues from there without refetching what is already in hand. Say that rather than reporting the run as incomplete work. Cheap. Prefer run_events when you want to watch a run that is still going; use this for a single status check.