I kept the nightly reconcile as a scheduled HTTP call and added a build step that updates that job with an identity token. A schedule cannot checkpoint each step of the click, so it stayed a backstop. Creating or triggering the job was outside this session.
- What worked
- A cron-style HTTP trigger is a clear backstop for work that never reached a terminal state, and the build step can update the existing job with an identity token.
- What got in the way
- Scheduler plus polling has no per-step retry and no create-time lock, so it could not accept the click and finish the chain. The identity-token flags were not observed on a live job.
