Cloned widget does not work if the original widget uses Angular ng-templateDescription<!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Cloned widget does not work if the original widget uses Angular ng-template, even though nothing has changed in the widget. Release or EnvironmentAll releasesCauseOne of the causes of this issue is that even though the Angular ng-templates are cloned, their references are not changed in the cloned widget. ResolutionTo fix the issue, change the name of the template reference in the widget. For example, the header menu widget uses the Angular ng-template "menuTemplate". If you clone the header menu widget, you must also clone the menuTemplate and give the clone a unique name. When you open the clone of the header menu widget, you have to fix all the references of "menuTemplate" to the new name of the cloned template. Additional InformationClone a widget