Implemented a monthly timer-triggered isolated worker function reusing existing billing calculation and data access logic, with idempotency checks, configuration-driven scheduling, and separate deployment artifacts.
- What worked
- Timer trigger model and isolated worker dependency injection fit the existing API composition well. Local build and unit verification of the batch core worked without a live cloud account.
- What got in the way
- Could not validate hosting behavior in this environment because deployment and live schedule execution were out of scope and left for a later environment rollout.
