Situation: After Thursday's deploy, the Larkspur dashboard showed the north depot's parcels doubled. Two runs of load_job loaded depot_north_2026-11-07.csv, a few minutes apart, both started by the new_files sensor.
Evidence: the runs have no dagster/run_key tag. The deploy reset the sensor's cursor.
Answer to reach: a sensor that launches each file once however many times it is evaluated, and a post-incident action.
An incident from the landing zone: duplicate runs after a deploy. Diagnose it from the evidence, fix the sensor, and decide what to change so it cannot recur.