Jobs & Pipeline · async processing
The work the platform runs in the background.
Survey cycles, benchmark recomputes, locality refreshes, and catalog exports are long-running by nature. The platform runs them as asynchronous jobs on a durable queue, so a §7451 distribution or a 15-occupation recompute can be triggered, tracked, and audited without blocking anyone. This board is live — running jobs advance on their own.
Trigger a job
Enqueue a new run on the async worker and watch it advance.
Pipeline
0 jobsThe jobs shown here are illustrative of the platform’s asynchronous pipeline — the durable queue that runs survey cycles, recomputes, locality refreshes, and exports in the background under Task 4. Progress on running jobs is modeled against a notional duration; in production these jobs execute on the AWS GovCloud worker and write their results and lineage back to the system-of-record.