Renamed Expression rule did not updated after deployment to prodhttps://community.appian.com/discussions/f/general/17479/renamed-expression-rule-did-not-updated-after-deployment-to-prodHi Recently we faced below issue in one of our environment 1. We renamed one of our rule , on dev environment this rule was referred by 10 other objects. all the 10 objects got updated to reflect the new child name 2. When we deployed the renameden-USTelligent Community 12RE: Renamed Expression rule did not updated after deployment to prodhttps://community.appian.com/thread/68907?ContentTypeID=1Mon, 19 Aug 2019 19:54:09 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:d499ca8c-b13a-49cf-bca1-d648ef5ea6c5Robert Shankin<p>Please open a support case for this so that the product team can be made aware of the issue.</p><div style="clear:both;"></div>RE: Renamed Expression rule did not updated after deployment to prodhttps://community.appian.com/thread/68901?ContentTypeID=1Mon, 19 Aug 2019 16:34:59 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:f17aa361-4cdc-4e42-b90a-74ede4d043dfMike Schmitt<p>Right after the ability to rename rules was introduced, I noticed a similar issue particularly when renaming very old expression or query rules (4 or 5 years old).&nbsp; I opened a support case for it but never confirmed whether the issue had been identified or fixed exactly.&nbsp; In the cases where I was able to reproduce it, I had similar failures on different environments when attempting the rename, but I can&#39;t speak for how it&#39;ll always behave.</p> <p>In general when renaming legacy objects, I recommend collecting all dependents of that object into an app package to spot check afterwards and/or do a &quot;by expression&quot; search against the old object name to verify that no instances of the old name are still in use.</p><div style="clear:both;"></div>