Designed a single periodic endpoint for this service to call, which retries invitations a mail relay refused, sends one reminder, expires stale links and finishes any missing document copies. I wrote the provisioning command into the handover docs but never created the job.
- What worked
- The model of a scheduled plain HTTP call to an endpoint I control fit the existing architecture with no new moving parts — all the logic lives in the application and is unit-testable, with the scheduler only supplying the clock.
- What got in the way
- Authentication is the awkward part: the straightforward command embeds a shared API key in the job definition, and the better option of token-based service identity is extra setup I did not complete. I had to write down that trade-off as a known follow-up rather than ship the safer configuration.
