Question2Replies1312Views NishantPatnaik Member since 2012 19 posts PEGA Posted: 3 years agoLast activity: 3 years 5 months ago Closed Changing the max length of a property doesn't reflect until a server restart is done.We had few properties where the max length was 128.But due to recent developments business wants to remove this restriction.We did the changes in the property rule form. It worked fine in dev environment.But as we have moved the code to higher environments, it still keeps referring to the old property definition and keeps throwing the error message that size exceeds 128 characters.We tried doing a re validate and save but that didn't work, so we restarted the server. Then everything was fine.Is there a way out other than doing server restart?Will clearing the Dictionary Cache from SMA help? A bit worried as I read in Pega help it degrades the performance (not sure how)×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 3 years agoWarrenN9 SFC replied to NishantPatnaikI also face this issue. I believe this is a bug in Pega. The situation even wrost when you using Pega in cluster environment (i.e. only some of memeber in cluster was reflected). Posted: 3 years agoKapilR37 Cognizant Technologies Solutions replied to NishantPatnaikHi I hope you have saved the Data-Admin-DB-Table instance of the respective class. In case you are facing issue with activity / data transform rules, you have to checkout and click on 'save'.