What is different about the server that is failing: Is it a standalone instance or Mongo cluster?

So it is the DAM Update Asset workflow that is failing? Did you modify it?What is different about the server that is failing: Is it a standalone instance or Mongo cluster?Simply overwriting the workflow may not fix the underlying issue.Regards,Opkar

Hi,what is appearing in your error.log file? The problem may be in your content and not your workflow, you need to get to the cause of why your workflows are going stale.Regards,Opkar

As jeers hinted, It is a warning and not an exception, so can be ignored. It should be reviewed if it occurs again, especially if it is thrown from custom code. But for now, this instance of the warning can be ignored.Regards,Opkar

Can you provide more details? Content migration from another WCM to AEM, migrating from one version of AEM to another? Which version of AEM are you migrating to?Regards,Opkar

Hi Andrew,I've been involved in Mongo projects and seen a few from a distance. From what I have seen, you must make sure you meet all the requirements for using MongoMK[0] and you must have a network/hardware available as specified in[0],key considerations such as RAM, Network speed(no cross region)...

Hi,while it is possible to run online compaction it is not recommended. If you do wish to use it, you should contact daycare who will work with you on using and monitoring online compaction, it should not be used without daycares approval for a production instance.If you are using offline compaction...

Only content for communities will be stored via MSRP. Comments etcRegards,Opkar

Did you do step 2 as defined in this page http://www.accunitysoft.com/sling-model-sightly-part/I think I had the same issue when I first used Sling ModelsRegards,Opkar

Hi,there is a specific section in the upgrade guide for authentication[0]Regards,Opkar[0]https://docs.adobe.com/docs/en/aem/6-1/deploy/upgrade.html