Since version 15.1
The issue was identified in the handling of Condition Record (CR) logic. Previously, when the validation of methods such as addOrUpdate() within evaluated CR logic returned an error, the affected entities were not saved. However, the processing logic would still conclude with an OK status, causing the overall CR processing task to appear successful. This situation could lead to data inconsistencies, as some entities were not actually created, despite the absence of error escalation. To resolve the issue, the system was enhanced so that warnings generated during the evaluation of CR logic at the calculation element level are now included in the Job Status Tracker (JST) messages.
Warning Message Example
Warnings for ID.TypeCode, logic: 'LogicName'
------------------------------------------------------------------------
<Warnings / Validation Messages>