@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.

@kautuk_sahni Sorry, i should have more clear. The rollout doesn't update the language master links if they are inside an RTE. I think that is still a common use case and remains un addressed. Can you or @Bimmi_Soi  confirm this please? I can create a custom rollout action to address this but i just...

@ASP_Corp invoke this workflow/ service from within an event listener that listens to replication events. when an asset is published, it will create a replication event that you can then listen to and invoke your workflow/logic to create asset versions.  Refer to the below on how to create an event ...

@stiegjo22 check this out - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-increase-max-number-of-parallel-workflows-on-assets/m-p/264283  

@SunitaCh3 This should work just fine with AEM as cloud service.

@priya_042  In this specific case, you are trying to modify/add jcr:created . You don't need to do add this property and the node will save without any issues.

@AkaneTo If the folders are created as ordered folders, then default alphabetical sorting will apply.