Report tables read the scraping platform's fact tables read-only (docs/DataSource.md §4 allowlist). No report is wired yet — this is the placeholder shell; each report endpoint is added under /api/reports/… as it's scoped.

— Beyond roughly 60 days Amazon will not serve the missing days again — re-enabling does NOT backfill. Age is measured from the last change to whichever switch is off — the marketplace's own, or the account's when the whole account is switched off. Scopes that are not collecting for other reasons (quarantine, or a seller who does not participate) are not listed here: they are not forgotten switches.

— Open an account to see its marketplaces grouped by region, with every account-level fact attached to the account rather than repeated on each market. A market is collected only when the account is on, the marketplace switch is on, the seller participates, and the account is not quarantined — the cause shown is the FIRST unmet one, so clearing it may reveal another.

— One write here affects EVERY account in that region. These are the hosts ADL sends requests to. Amazon publishes them; MD stores what Amazon publishes and never derives one from a pattern — the Ads na host carries no region suffix while eu/fe do, so any {prefix}-{region} rule is wrong for exactly one row.

— One bar per cycle over the window. Green = completed, red = failed. The line is backlog (queued at cycle end) — a rising line means the daemon is falling behind.

% of drain slots lost to 429 cooldown (skipped_cooldown / (executed + skipped_cooldown)). High & rising = quota-bound, not scheduler-bound.

Each date-bound report's newest completed day, with the lag it's expected to carry: today's Amazon data isn't queryable yet, so a lag of a few days is normal and healthy. "Status" is DL's own on-time verdict (lag vs. expected). Snapshot reports target "now" and carry no lag.

Per target-date completion. Done % / Achievable % count task ATTEMPTS (op_tasks rows), so a slot that was throttled (429) then recovered leaves both a failed and a completed row and reads low forever — they show retry churn, not data truth. Real % is the data-truth view: of the distinct slots (account×marketplace×report) attempted, how many NOW have data (joins the catalog), excluding structural ceilings (no Ads profile / no data). Real % is typically ~99% even when Achievable % dips to ~87% on maturity-refresh peak days — the dip is a counting artifact, the data is there. Failures split into structural (permanent ceiling) and recoverable (a retry could clear).

Everything above is Amazon DL's health. This is ours: for each market, when did a refine last succeed, and did any fail? A failed refine writes no rows — so without this panel a broken sync looks exactly like a market with no sales. Unknown means the run predates outcome tracking, not that it's healthy.

— One bar per scrape cycle over the window. Green = completed, red = failed, sized against the cycle's executed count.

Whether the upstream Walmart data shape still matches what the refine expects. An unacknowledged breaking change means the refined output may be wrong until reviewed.

— Per-SKU monthly roll-up from the daily detail. Rates (ACoS/TACoS/CVR) are computed over the month (spend÷sales, not a mean of daily rates). Click a header to sort. Default hides inactive SKUs. Money in the marketplace's native currency.

— Pick one or more markets and press Load.

— · Pick markets above, then Load.