The error is related to scene7 and Asset's Scene7 ID is not available. Can you please check if this asset is uploaded properly in Scene7? Is there any configuration related to Scene7 which is updated recently. Please check the assets which are getting downloaded are also synced to Scene7.

Please check if there is any error in browser console. Also please check if same behavior is observed in OOTB sample website as well, to verify if any of your custom code is causing this issue. 

Yes, thats true. Quick site feature is available only in Cloud Service at present. 

@HarshaVardhan21 Quick Site feature is available in AEMaaCS only. Please confirm which AEM version you are using.

@Anoop_Garg  Nope that is not possible. You can create a sample project for same AEM version with latest archetype and compare the differences. There might be some dependency version updates would be there that will make your project more compliant apart from that I dont think there would be any maj...

So the error is  "Failed to create a S7 IPS job". Try following things if it helps Check Scene7 configuration if connection is still getting established.Install  Dynamic Media Classic desktop application as you can see reason of failed job with details.Create a log file set to debug level for follow...

Thanks for updating. Can you please also try this : https://experienceleague.adobe.com/docs/experience-manager-65/deploying/practices/best-practices-for-queries-and-indexing.html?lang=en  

@girishb83316758  Please check the server logs. Server log file should have exact root cause. It looks like indexing issue as you are able to fetch result/run query in child folder properly.

Is there any reason we are looking on metadata instead of data?GraphQL works on the schema that we define in the content fragment model whereas the property you are referring is the properties of an Asset. Whatever fields Author edits of a CF schema/model, are saved on this location : PATH_CF/jcr:co...

Please check the log file to get the exact root cause. There could be a connectivity issue between your server and Scene7. Please share logs to help you further.