Warranty records do not process Contract clm_condition_check records via BR, but they process in the daily jobDescriptionWarranty records do not move out of their initial state after approval, while Contract records on the same flow update immediately. The user sees no state change when approving a Warranty — the record stays in its Draft/approved state until the daily Contract Compliance Checks job runs overnight, which then applies the contract rules and transitions the record. So a Warranty approved during the day sits in an incorrect state for up to 24 hours, and the approval action behaves differently based on the contract type. Steps to Reproduce Create a Warranty record, save and approve it.Observe that the state does not update after approval.The state only updates when the daily "Contract Compliance Checks" scheduled job runs.Repeat the same steps with a Contract record — the state updates immediately on approval.WorkaroundApply the update set XML file attached to this article to the affected instance: Download the attached update set XML file from this article.Log in to the affected instance using administrator credentials.Navigate to System Update Sets → Retrieved Update Sets.Under Related Links, click Import Update Set from XML.Choose the downloaded XML file and click Upload.Open the new retrieved update set (its name will be shown at the top of the list) and click Preview Update Set.Review the preview. If any conflicts or missing ancestors are reported, proceed accordingly: For customized records, accept the incoming update where appropriate, or skip and reapply after review. Click Commit Update Set once the preview completes without blocking errors.After the commit completes, create a Warranty record, save and approve it, then confirm the state updates immediately on approval without waiting for the daily Contract Compliance Checks job.Related Problem: PRB2084757