Hi @Jörg_Hoh , I am trying to automate the content sync between two AEM CS author instances and was trying to sync the content using Forward Sling distribution on the basis of triggers , I created a custom queue with my target import instance as another author , but the sync is throwing above error ...

Hi @Jörg_Hoh ,  I am not trying to do reverse replication , i am trying to sync content between two cloud author instances using SCD Forward sling distribution , but when triggering the queue getting below errororg.apache.sling.distribution.common.RecoverableDistributionException: not enough rights ...

@VictorToledo , one more point to consider , that there is no active reference of the asset on the site author pages.  Thanks

Hi @binary0010 , have you got the solution to this , we are getting the same error on cloud , on my local cloud SDK , i am getting same error , i am using admin user with full access on /content Thanks

Hi @aanchal-sikka , have you tried this in the past , actually my requirement is to create the multiple package of site pages which would be roughly less 300 MB and move them from one cloud instances to another across the org  via automation , be it CI/CD scripts or programmatically at AEM level and...

the retry just keep on increasing the build count set by the package manager API 

hi @pulkitvashisth , i tried this flag it does not hold the connection for 600 seconds , it fails after every 60 seconds and go to next try till the retry count exhaust  Thanks

Hi ,  I am using curl command to build the package (eg 250 MB) , but it times-out when the package is big and throws 503 error , but the package keeps building in the background and finally i can see a proper build package in the package manager , Can we increase the timeout of curl command and also...

For this usecase Vlt wont work until CRX is blocked on cloud environment, best is to work with Adobe for their opinion and evaluate the options

In AEMaacs , devs dont need osgi console access and it is also not accessible to developers on cloud author environment . we just have developer console access in cloud. so the only way to push osgi configurations are through code Thanks