Sorry.. its 'Absolute Time Auto Advancer' which is on the top of the dropdown in your screenshot

Hi, For your use case please use 'Advance Time Auto Advancer' handler instead of 'Auto Advance' and set the time required as 24hrs. It works I have tested it on AEM 6.1.

It didnt work either for me, I am trying to see what is there in AutoAdvancer meanwhile as @will mentioned, do you want to try to Advance Time Auto Advancer

In the document it says"This process automatically advances the workflow to the next step. If there is more than one possible next step (for example, if there is an OR split) then this process will advance the workflow along the default route, if one has been specified, otherwise the workflow will n...

Actually not, it talks about AEM 5.6.1 itself but it does mention that with Oak in AEM 6.x, you can create much more nodes without any performance hits

As you mentioned, there is no limit on the max number. However, we can restrict to some arbitrary number considering the performance. [1] is a good read about it[1] https://cqdump.wordpress.com/2015/07/09/1000-nodes-per-folder-and-oak-orderable-nodes/

Hi Selva,As @Scott and @Opkar mentioned you, path of a page in a publish will be same as the path in the author. If you need to make any performance testing, you can do it on the same path in AEM Publish of a non-production instance. If you can tell us your actual use case, we can try to give you a ...

So in the same document, it has mentioned to set that as part of configuration. So you can mention as part of your Mongo URI configration in AEM as below via ConfigurationIn this mode the config is specified as part of the Mongo URI (See configuration). So if a user wants that reads from secondaries...

You can still use 1.8 unless you see any errors while setup

you have to write a listener and check the value of each field. refer [1] to know about listeners[1] https://docs.adobe.com/docs/en/aem/6-0/develop/components/widgets.html