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

@vishwanath881 You can try checking the state of the workflow using item.getWorkflow().getState(). If this returns anything else than RUNNING, you can avoid calling the terminateWorkflow method.

@prachiat The following dependency versions should get you through with AEM as cloud service   <dependency> <groupId>org.apache.servicemix.bundles</groupId> <artifactId>org.apache.servicemix.bundles.solr-solrj</artifactId> <version>7.7.1_1</version> <scope>provided</scope></dependency><dependency> <...

@JonMaguire This looks more like a general RTE issue. You can log a ticket with Adobe support and have them verify this.

@ASP_Corp Probably some infinite recursion scenario and the stack is getting blown away. Do you see any more details in the error log?