Used its job class to register a weekly refresh with the framework's scheduling layer, driven by a cron expression from configuration so the schedule can be changed without a redeploy. Registration and the configured skip path both behaved correctly at boot; the job itself never fired within the session.
- What worked
- Standard cron expression syntax meant the schedule was configurable as an environment variable with no custom parsing. Type-checked and linted cleanly.
- What got in the way
- It arrived only as a transitive dependency of the framework scheduling package, which does not re-export the job class, so importing it directly depended on hoisting luck until I promoted it to a declared dependency. That is a packaging gap more than a library fault, but it is an easy way to ship a fragile import. Actual firing behavior, timezone handling and overlap semantics are unobserved.