Following are the best practices in my experience:Avoid using queries and custom indexing for your components until necessary.Resolve browser error for your applicationLook for errors or exceptions in logs.Tune in the maximum number of concurrently running workflow processes for Asset processing.Clo...

Add the below lines in config.xml of oak:index :<tika jcr:primaryType="nt:unstructured"> <config.xml jcr:primaryType="nt:file"> <jcr:content jcr:primaryType="nt:unstructured"/> </config.xml> </tika> 

Check the permission of the workflow group which is triggering the custom scheduled activation workflow.It seems the group does not have the permission.

I'm using multifield, and no issue is there.  Could you provide the AEM version, and are you using Multifield (i.e. granite/ui/components/foundation/form/multifield)?  

@pradeepdubey82   :Check https://experienceleague.adobe.com/docs/experience-manager-learn/foundation/development/set-up-sling-dynamic-include.html?lang=en for SDI.

The model should use adaptables either as SlingHttpServletRequest.class or Resource.class and should not use both.

2_property has type= cq:Payload instead of cq:Workflow , so the query will not return results.So, the above query cannot run with two properties.It will run independently as properties are stored in different type:path=/var/workflow/instances/server0 type=cq:Workflow 1_property=modelId 1_property.va...

Check  https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-blogs/aem-dispatcher-setup-made-easy-with-docker-aem-community-blog/ba-p/411862 and see the command to run docker.

Checkout https://experienceleague.adobe.com/docs/experience-manager-65/developing/components/json-exporter-components.html?lang=en  explains the concept of JSON exporter to export JSON from Model.

You may need to write a PostProcessor (code to trigger when SSO login is done) to check user permission for a particular asset.