Unexpected RuleApp version deployed to Rule Execution Server
I am deploying RuleApp testRuleApp with major version 1 and minor version 1 in Decision Center to Rule Execution Server (RES) using "Increment RuleApp minor version".
RES already has the following versions of this RuleApp from Explorer > RuleApps:
testRuleApp 1.0
testRuleApp 2.0
testRuleApp 2.1
testRuleApp 3.0
testRuleApp 3.1
testRuleApp 1.1 is added instead of testRuleApp 3.2 as a result of increment RuleApp minor version.
This is the expected behavior as the versioning policy of RuleApps applies only when there is a conflict in the versions. If the RuleApp does not exist, it is deployed to RES irrespective of the selected deployment policy.
For your example, this version does not exist in RES server memory, it is added directly without using the deployment policy, therefore you got testRuleApp 1.1 in RES.
Refer to this documentation for more details of the RuleApp versioning policy.