November 2026
Prevent concurrent QOps writes to the same app and show who holds the lock
When another QOps run is already writing to the same app, QOps-Build, QOps-Release, and in-place QOps-Publish runs stop at once without changing it and report the user, machine, and start time of the active run — regardless of which account or machine started it. Pass -WaitAndRewrite to wait up to 10 minutes for the other run to finish before writing, or -IgnoreWriteLease to write immediately when you are sure the lock was left behind; both flags are also available under Flags in the Portal. A lock left behind by a run interrupted mid-write is treated as stale after 60 minutes (configurable via WriteLockStaleMinutes), after which the next run removes it and continues. While an app is reloading, QOps skips writing and reports it (or waits if -WaitAndRewrite is used).
This protection applies to Qlik Cloud. On Qlik Sense client-managed, runs on the same app are not yet kept apart.