[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-changelog\u002Finfra-wake-schedules":3,"docs-tabs-changelog\u002Finfra-wake-schedules":6},{"content":4,"lastmod":5},"# Change history: Scheduled wake\n\n[← Changelog](\u002Fdocs\u002Fchangelog). Entries: 12.\n\n- 2026-10-09 [FIX-1009-12: wake windows: margin no lower than the platform's, outcomes by the moment the server came up](\u002Fdocs\u002Fchangelog\u002F2026-10-09#fix-1009-12-wake-windows-margin-no-lower-than-the-platform-s-outcomes-by-the-moment-the-server-came-up)\n- 2026-09-25 [FIX-0925-18: a wake window on a server in the scheduled run mode can be created and edited through the API](\u002Fdocs\u002Fchangelog\u002F2026-09-25#fix-0925-18-a-wake-window-on-a-server-in-the-scheduled-run-mode-can-be-created-and-edited-through-the-api)\n- 2026-09-22 [FIX-0922-13: a wake schedule can be set for an app inside a galaxy again](\u002Fdocs\u002Fchangelog\u002F2026-09-22#fix-0922-13-a-wake-schedule-can-be-set-for-an-app-inside-a-galaxy-again)\n- 2026-09-17 [FIX-0917-17: the idle threshold on a scheduled server is no longer a silent no-op](\u002Fdocs\u002Fchangelog\u002F2026-09-17#fix-0917-17-the-idle-threshold-on-a-scheduled-server-is-no-longer-a-silent-no-op)\n- 2026-09-16 [FIX-0916-10: a wake window on a server with a run mode is no longer refused as an always-on conflict](\u002Fdocs\u002Fchangelog\u002F2026-09-16#fix-0916-10-a-wake-window-on-a-server-with-a-run-mode-is-no-longer-refused-as-an-always-on-conflict)\n- 2026-09-09 [FIX-0909-8: the spec declares the 429 refusal of endpoints that carry their own rate limit](\u002Fdocs\u002Fchangelog\u002F2026-09-09#fix-0909-8-the-spec-declares-the-429-refusal-of-endpoints-that-carry-their-own-rate-limit)\n- 2026-07-22 [NEW-0722-2: scheduled wake (wake-schedules) is now available on every Bitrix24 account](\u002Fdocs\u002Fchangelog\u002F2026-07-22#new-0722-2-scheduled-wake-wake-schedules-is-now-available-on-every-bitrix24-account)\n- 2026-07-16 [NEW-0716-7: preemptible-plan advisory in scheduled-wake responses](\u002Fdocs\u002Fchangelog\u002F2026-07-16#new-0716-7-preemptible-plan-advisory-in-scheduled-wake-responses)\n- 2026-07-10 [NEW-0710-1: wake-schedule window management (wake-schedules)](\u002Fdocs\u002Fchangelog\u002F2026-07-10#new-0710-1-wake-schedule-window-management-wake-schedules)\n- 2026-07-10 [NEW-0710-2: machine-readable tz-warning code in wake-schedules responses (`tzWarningCode`)](\u002Fdocs\u002Fchangelog\u002F2026-07-10#new-0710-2-machine-readable-tz-warning-code-in-wake-schedules-responses-tzwarningcode)\n- 2026-07-10 [FIX-0710-3: wake-schedules: schedules rejected on always-on servers](\u002Fdocs\u002Fchangelog\u002F2026-07-10#fix-0710-3-wake-schedules-schedules-rejected-on-always-on-servers)\n- 2026-07-10 [FIX-0710-4: wake-schedules can now be declared on nested galaxy apps](\u002Fdocs\u002Fchangelog\u002F2026-07-10#fix-0710-4-wake-schedules-can-now-be-declared-on-nested-galaxy-apps)\n",null,{},1794739512391]