@kautuk_sahni  This is probably coming out of an old AEM archetype. You can mark this as not relevant to the current archetype versions. 

Request for Feature Enhancement (RFE) Summary:Enable Rollout of Cq:tags property by default for content update and other relevant MSM  configsUse-case: In AEM page properties basic tab, the Tags field is excluded from rollout to Live copies. This is due to an exclusion rule applied in MSM content up...

@SarahBo2 Probably the issue is with antisamy or XSS sanitization.  Refer to this article if that  is the case - https://aemcorner.com/rte-open-in-new-window-not-working/  

@neo-silicon In that case, adding a CUG to a page will prevent end users from accessing it and hence the 404.

@neo-silicon Is your end-user part of this admin group? if not, shouldn't this be expected?

@AlexNathanson AEM is backed by Java content repository(JCR) and as such any resource update works on an 'eventual consistency' concept. So if you have multiple updates on a resource, they will be combined (as best as possible by JCR). Coming to AEM Pages, there is an explicit way to lock pages to p...

@SivaNa3 You can create a simple groovy script to update all component instances. Additionally, to avoid breaking your pages/components. add a default value to this new field.

@MithraDe if you just need this list, You can create a ACS commons report to look for all workflow instances under /var/workflow/instances. You can then filter it based on attributes like modeId, status, start_time etc. Hope this helps.

@SUNITACH2 Are you running this build locally or is this error coming out of a pipeline build ? 

@ASP_Corp considering extensibility in mind, i doubt if that is an overkill. Also, when you plan to move to AEM as cloud service, you will have to switch to post processing workflows instead of launcher based implementations. Food for thought.