fix(plugin-reports)!: a non-member schedule timezone no longer discards the cron expression #22787
pr-automation.yml
on: pull_request
Check PR Size
15s
Check Changeset
58s
Auto Label
15s
Annotations
1 notice
|
Check Changeset:
.changeset/report-schedule-timezone-guard.md#L0
ADR-0087 exemption (no-migration-prescription): No metadata moves. No key is retired, no def is unpublished, no schema shape changes, and `sys_report_schedule`'s declaration is untouched apart from a comment — so `objectstack migrate meta`, `spec-changes.json` and the upgrade guide have nothing to rewrite and no ledger entry would have anything to say. The obligation this change creates is DATA-SIDE and operational, not a code rewrite: an operator checks `sys_report_schedule.last_status` for `failed` and corrects the row's `timezone`, and the schedule resumes on the next sweep by itself. That channel is the row the operator is already looking at, which is strictly more precise than a migration-chain entry about a metadata surface that did not change.
|