Is there any dispatcher in front of AEM when you are trying to hit? It does not seem to be usual that you are getting bad request and AEM is actually receiving the request. Did you see anything in request.log?

You can use rendercondition as explained by @aanchal-sikkaIf possible please avoid doing such customization as you may face issue with upgrades.

@RooRue If Asset is still linking to its old version, can you please try purging older versions and see if it helps. https://experienceleague.adobe.com/docs/experience-manager-65/deploying/configuring/monitoring-and-maintaining.html?lang=en  

@skumari Please update if your local issue got resolved and what was the fix. It will help others as well.

@skumari I think in that case AEM is corrupted. AEM creates a folder inside crx-quickstart where it stores blobs and segment store by default. Probably the user you are using does not have full privileges and due to that AEM is not able to create blobs inside crx-quickstart.  Check permissions befor...

Hi @skumari Once you setup AEM, please check if all bundles are active and AEM looks in healthy state. Try opening any we-retail pages. I hope you are setting up AEM with all required permission in the beginning.  Once AEM looks stable, please install any package created from different env just to v...

@pragya96  As Kiran also requested, please share error.log or error details.

Hi @RobertHarperFS,There are inner dependencies that gets added as Import packages and causes bundle to be in Installed state. You can neglect those dependencies and try testing your functionality which is using third party dependency if all is working fine once bundle is active. You can neglect suc...

@P_V_Nair Please confirm By oak sync you meant crx2oak sync?I have done similar task for around 2 lakh assets which is way to less compared to 7 million in your case. As requirement is to sync Assets to DM and publish,I dont think you need to run DAM Update workflow as it do lot of other checks whic...

When you start the workflow using workflowSession, it starts the workflow in a different thread. So your Scheduler wont know whether it will be getting failed or not. You should refactor your workflow logic/process to avoid getting failed. There is a thread based approach to validate the status of w...