Queue an individual application refresh

Paid plans, including Developer, can queue a source check for a stored application. No request body is required. Supported routes are active, live IDOX council detail routes and Stratford-on-Avon's native application detail route; unsupported routes return 409. A 202 response confirms queue acceptance, not source-check completion. Pending/running requests are deduplicated per application across callers. After a recent request, including a failed attempt, new requests are subject to a one-hour cooldown; pending/running work is reused first. Refresh POSTs, including authenticated duplicate/cooldown requests, and subsequent GETs consume the normal API allowance. The background council check is not an additional customer request. The server scheduler checks queued work every minute with bounded sequential processing, but source health holds and load can delay or prevent completion; no one-minute completion guarantee applies. Failed checks are retained, not automatically retried by the individual endpoint. Save the prior freshness fields, then read the application again: a newer recordCheckedAt confirms success, a newer recordCheckFailedAt records failure, and unchanged timestamps do not establish completion. Use the batch endpoints when queue progress and per-reference outcomes are required. Initial refresh enriches status/decision for undecided records and preserves known decisions; it does not refresh documents or reconstruct full stage history.