I spent two full weeks trying to fix a similar cycle during the deal closing phase. Each time, I resorted to external solutions; the built-in mechanisms simply weren't good enough to handle edge cases. The default settings, frankly, are a trap for anything beyond the basic functionality.

When the built-in trigger layer consistently fails, the problem is usually that the platform evaluates conditions at the wrong point in the pipeline, rather than when a field changes. In Bitrix24, creating custom automation rules that target individual fields rather than transitions between stages typically solves this problem. For example, custom automation rules can be found here http://roboteka24.com/ The underlying logic avoids the timing gap described by regularPost by tying each robot to a specific field state rather than a broader event.