{"version":"2.1.260","anchor":"new-relaunch-window-control-for-served-config-changes","canonical_anchor":"new-relaunch-window-control-for-served-config-changes","heading":"New relaunch-window control for served config changes","tier":"use","area":"Admin Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/new-relaunch-window-control-for-served-config-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### New relaunch-window control for served config changes\n\nA new setting controls how long you can keep working on stale config before a forced restart.\n\nA new `relaunchEnforcementHours` setting controls how long a user can keep working on a stale config after the server pushes a change before the app forces a restart dialog. It defaults to 1 hour, is settable from 0 to 336 hours, and only takes effect when set via the remote bootstrap config; it is ignored if set via MDM.\n\n- Area: Admin Settings\n- Names: `relaunchEnforcementHours`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 1\/5"}