# Work time Configure UTC time windows for each module. Outside the window, the module sleeps. Inside, it runs normally. Default: 24/7. ## How it works Every module has an optional **Work Time** setting with **Start** and **End** fields in HH:MM format (24-hour, UTC). - **Not set:** module runs 24/7 (default). - **Start = End:** treated as 24/7 (no window). - **Start < End** (e.g. 08:00–20:00): simple daytime window. - **Start > End** (e.g. 22:00–06:00): overnight window crossing midnight. Each module has its own independent work time — one module can run 08:00–20:00 while another runs 24/7. ## Overnight crossing When Start is later than End, the module is active from Start to midnight AND from midnight to End. Example: setting Work Time to 22:00–06:00 means the module is active from 22:00 UTC to 05:59 UTC. ## Configuration Work Time is set per module in the module's settings panel. Enter the **Start** and **End** times in HH:MM format (24-hour, UTC). Leave empty for 24/7 operation. Valid range: 00:00 to 23:59. ## Runtime behavior - When a module cycle starts outside the work window, it pauses until the window opens. - While paused, the module checks for stop commands every 60 seconds, so it responds to manual stops within a minute. - Once the window opens, the module resumes its cycle immediately. Strategy guide: [Work-Time Windows & Timezone Strategy for X](https://helperx.app/blog/work-time-windows-timezone-strategy) — why 6–10 hour human blocks beat fake 24/7 presence.