Latest Records Re-Upload Later Window
โถStep 3: Re-Upload With A Later Window
Upload the same facility file again, changing only end_date to
2025-12-31. Captures latest_records_second_task_id.
โถWhat this step does
It creates a second ingestion task, and a second record of every facility in the file. Nothing is edited and nothing is deleted โ the step 1 records still exist, exactly as they arrived.
This is the behaviour the whole workflow exists to explain. Re-uploading adds records; it does not update them.
โถforce: true is required here, not optional
force: true is required here, not optionalThe duplicate-upload guard rejects an upload whose file content and
processing parameters match an already-completed task. end_date is not one
of the parameters it hashes โ only location_type, commodity_type,
metrics, assessments, metric_options and metric_confidence_levels are.
So this upload, which changes only the window, has the same fingerprint as step
1 and is rejected without force. Anyone re-uploading a file to move its
monitoring window forward hits the same thing.
โถWhy the later end_date
end_datemonitoring_end is key 2 of the six-key precedence, so the record with the
later window takes currency. Re-uploading with the same window would not
reliably supersede anything: keys 1 and 3 prefer a record whose location
already has metric results and assessments, which the step 1 record may have
and this one may not.
Both dates are Dec 31 of a prior year deliberately. end_date also accepts any
date in the current year up to today, but such a date is rejected once the year
turns โ two prior-year year-ends keep this workflow runnable indefinitely.
โถNext Step
โ Step 4: Wait For The Re-Upload โ the currency stamp is written during processing.