Robin Shen [18/Jan/18 08:05 AM] There are several ways to do this, pause the configuration at source configuration side, pause the whole system at target QB instance side, etc.

J. Mash [05/Feb/18 05:13 PM] Please consider the use-case of moving configurations from a "development" environment to a "live" environment, particularly on installations that support multiple large projects:   - Pausing the entire system does not allow builds to be triggered easily, as it forces all builds into a "queued" state while the system is paused.   - Pausing the entire system does not prevent builds from being scheduled, merely forces them into a "queued" state while the system is paused.   - Pausing the entire system to update a single project's configuration is extremely heavy-handed, as it requires complete service interruption for all projects, not just the one being updated.   - Walking through all configurations to be copied and disabling/enabling them explicitly (and then having to do the reverse later) is not always as simple as it sounds with large projects. The purpose of this request was to minimize the impact of a system-wide pause and make the process of disabling/enabling scheduled builds substantially less arduous and error-prone.