A: No. RTGI has a failsafe; forcing a release without fixing the underlying cause leads to a split-brain state where different nodes run different release versions. This causes data corruption.
In plain English: The deployment system attempted to promote a new release (e.g., version 4.2.1 to 5.0.0), but the runtime environment reported an inconsistent state. This could be due to residual files, locked registry keys, orphaned processes, or corrupted cache from a previous release. rtgi 01702 release fix
A: The latest RTGI versions (3.x and above) introduced distributed locks and atomic release transactions, drastically reducing the frequency of 01702. Upgrading is strongly recommended. A: No. RTGI has a failsafe