I have a content fragment which has references to audio files from dam. I'm exposing a graphQL endpoint which pulls contents from this content fragment and exposes publish url of contents. In the response, I'm getting the url of the audio like : https://publish-pXXXX-XXX.adobeaemcloud.com/content/da...

@aanchal-sikka 1. I have started local instance in normal mode only. Even in "dynamicmedia_scene7" runmode, it doesn't work.java -jar aem-author-p4502.jar -r dynamicmedia_scene72. I have pulled all the images from higher environments to local.3. Yes they are published in higher environments and Its ...

Yes in local instance, both author and publish. Yes, dynamic media is setup. I have setup DM settings in local by bringing the changes from conf/global/settings/. But the connection is failing. But it works in higher environments. What am I missing?  

I want to get the content of a page as json and I want to consume that from an external application. When I tried in author, it works. But it doesn't work in publish instance. Please help on how to make it work on publish instance.Thanks.

@aanchal-sikka Url is different. It's something like 'adobe/dynamicmedia/deliver/....'

Images are not loading in AEM pages though they are available in dam. See the below screenshot. In browser console, I get 404. But I have those images in dam and the path given is correct too.But the image loads in higher environments (AEM as a Cloud Service). I think I'm missing something in my loc...

Hi @iamnjain ,1. I dont see any error. I get a notification saying 'selected query scheduled for publishing'2. Throws an error. curl: option --header: requires parameter

I'm using the default cache headers values for graphQL queries. 

Hi @maheshp ,Thanks for the response. How do I get the publisher IPs?It's a cloud instance.Replication queue looks ok. 

Hi Team,When I make changes to Content Fragments, Models and GraphQL query and publish all of them, I don't see the changes reflected in publish instance. I could see them in author instance though. I waited for about 30 mins, still I don't see them in publish. I'm checking this in dev environment.I...