Question
Adqura
IN
Last activity: 1 Dec 2025 21:43 EST
Cannot Checking an Email treatement which was saved as from an older ruleset version.
I have saved as an Email treatment from an older Ruleset verison. After making my changes I tried checking in, but I am getting this error message. This used to work fine previously.
HCA Healthcare
US
@SHUBHAMK16910693 This issue usually happens when the Email treatment is saved in a ruleset version that is not active for your application. Can you first check which ruleset and version your application is using in the Application rule. Then open the Email treatment and do a Save As into the latest unlocked ruleset version that is in your ruleset stack. Make sure that ruleset version is added to your access group and is at the top of the stack. After saving into the correct ruleset version, discard the old checkout if it still exists. Now try to check in the treatment again from the new ruleset version. If it still fails, create a new higher ruleset version, move the treatment there with Save As, and repeat the check-in. Thanks
Adqura
IN
@SairohithThank you so much for replying to my post. I have checked it thoroughly my ruleset version is active for my application. Plus the ruleset from which I am saving this rule is also accessible for my application. Can you please suggest any other solution, as of now i tried saving it with a different name and it is working fine. But creating the same rule with a different name in a higher RSV is not an optimal solution. I am looking forward for your solution. Cheers.
HCA Healthcare
US
@SHUBHAMK16910693 If the ruleset version is active and unlocked, and the same rule works only when you change the name, it usually means there is a conflict with an older version of that treatment. First, search for the treatment with “All versions” and make sure there is no checked-out copy (yours or someone else’s) and no older version marked as Blocked or Final. If you are using CDH / 1:1 Operations with Revision Management, check whether this email treatment is part of a closed or active revision – if so, you must change it through that revision instead of Dev Studio, otherwise check-in will fail. In that case, create a new change request/revision and modify the treatment from the 1:1 Operations portal so the platform manages the check-in for you. Another option is to Save As the rule into a higher, unlocked ruleset version with the same name and then mark the older version as Withdrawn so only the new one is picked by rule resolution. If you still see the error, ask your admin to confirm there is no lock or governance setting on that rule type/ruleset after the 24.2.2 upgrade.