fix: no cron time zone on repeat-seconds worker schedules #17

2026-10-14T20:03:10Z

KofTwentyTwo commented

2026-10-14 20:03:10 +00:00

(Migrated from github.com)

OutboundProcesses.process set cronTimeZoneId("UTC") on every worker schedule, including the repeat-seconds ones (edi_outbound_worker, edi_send_worker, edi_as2_mdn_sender, edi_ack_monitor). Core instance validation refuses a time zone on a non-cron schedule ("a non-cron schedule must not specify a cronTimeZoneId"). So any host that configures a scheduler fails validation at startup. kof22 hit this while adopting 0.1.0-RC.4 (KofTwentyTwo/Website-Backend#225 carries a marked host stand-in until this ships).

Only cron schedules get UTC now. OutboundTest.repeatSchedulesHaveNoCronTimeZone covers both cases.

./mvnw -B verify: 243 tests, 0 failures; checkstyle clean; coverage met. Ask: include in 0.1.0-RC.5.

🤖 Generated with Claude Code

`OutboundProcesses.process` set `cronTimeZoneId("UTC")` on every worker schedule, including the repeat-seconds ones (`edi_outbound_worker`, `edi_send_worker`, `edi_as2_mdn_sender`, `edi_ack_monitor`). Core instance validation refuses a time zone on a non-cron schedule ("a non-cron schedule must not specify a cronTimeZoneId"). So any host that configures a scheduler fails validation at startup. kof22 hit this while adopting 0.1.0-RC.4 (KofTwentyTwo/Website-Backend#225 carries a marked host stand-in until this ships). Only cron schedules get UTC now. `OutboundTest.repeatSchedulesHaveNoCronTimeZone` covers both cases. `./mvnw -B verify`: 243 tests, 0 failures; checkstyle clean; coverage met. Ask: include in 0.1.0-RC.5. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: QRun-IO/qbit-edi#17