How can be reverse replicate users created on publish environment to author environment?
I tried to create workflow launchers for Reverse replication workflow on event "node created" of type "rep:user" but workflow is failing.
I am getting this workflow exception
com.adobe.granite.workflow.WorkflowException: Process execution resulted in an error
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: com.adobe.granite.workflow.WorkflowException: Failed to execute process
... 8 more
Caused by: com.day.cq.workflow.WorkflowException: javax.jcr.PathNotFoundException: /home/users/community/c/EN1McTKEo6NWDyHWaf_Z
... 9 more
Caused by: javax.jcr.PathNotFoundException: /home/users/community/c/EN1McTKEo6NWDyHWaf_Z
... 10 more
In order to workaround the error, you can try to exclude /home/users/community from your workflow launch configuration or add sufficient permissions to /home/users/community for workflow-service account.
Thanks for your reply but in the same article following is writter
" As of AEM 6.1, when user synchronization is enabled, user data is automatically synchronized across the publish instances in the farm and are not created on author."
So doesnt it means user sync works only among publish environments and not from publish to author.
My bad I did not read your question clearly.
Sling distribution is only to synch users among multiple publishers
Hi i gave all required permissions now workflow is not throwing any error and it is getting completed successfully but user is still not getting replicated to author.
On the communities console in author, You can go to the member's tab and it will show you all the users on author. It uses a tunnel service to get users from publish instance.
So, instead of using reverse replication, you can leverage the Tunnel service feature. Check the "Tunnel Service on Author" at 
Once I enabled the tunnel service I was able to see data of users in community console but they were nor present under /home/users.
Is there any way we can reverse replicate the node structure as well.
e.g. if a user is created on publish, it should be reverse replicate to author.
Can you share the usecase where you require users on author as well? As per the design, you should use tunnel service to check the users but all operations should be performed on publish side.