Identify the business period
For a daily export, distinguish the scheduled start from the period being exported. Define the timezone and the start/end boundary. Kubernetes documents that a CronJob can create two jobs or none in some circumstances; a business process still needs its own completion record. This does not imply that every scheduler behaves identically.
| Period | Expected | Observed | Decision |
|---|---|---|---|
| 2026-10-07 HK time | One accepted export | One file; target receipt exists | Complete |
| 2026-10-08 HK time | One accepted export | No receipt | Inspect output before rerun |
| 2026-10-09 HK time | One accepted export | Two attempts, same period | Match destination; keep one business result |
Recover a period without shifting its meaning
A catch-up run should take the missing period as an explicit input, not silently use today’s date. Freeze its selection boundary or record the extraction snapshot so late edits have a defined treatment. Check row count, rejected rows and destination acknowledgement before closing the period.
The job exits successfully but the destination accepted 96 of 100 rows. Is the period complete?
Show the worked answer
Record partial completion and identify the four rejected identities. Correct or disposition those records, then reconcile them without resending the 96 accepted rows blindly.