Hi @Keerthi0555    Can you please update the post with your issue? If your issue is resolved, please let us know to close this question.   Thanks, Kiran Vedantam.

Hi @rkmk107    Can you check if the bundles are active in the publish instance? Also, check the core components' status - I sense its issue with them.   Thanks, Kiran Vedantam.

Hi @anna_tech    Can you please confirm if this issue is related to AEM? If not can you please post it in the appropriate channel for a quick response?   Thanks, Kiran Vedantam

Hi @Ganthimathi_R    Try this: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/unable-to-connect-to-any-backend-in-farm-publishfarm/td-p/558619#:~:text=Try%20to%20clear%20the%20cache,issue%20is%20with%20the%20docker.   Hope this helps.   Thanks, Kiran Vedantam

Hi @kevingtan    Can you check if your bundles are active? Also, instead of copying the node altogether, you can proxy the component and refer it to core components page.   Thanks, Kiran Vedantam.

Hi @pragya96  Can you possibly share the error.log or any errors that you see in the console? Thanks,Kiran Vedantam

Hi @sxmalone  Is this issue seen in AEM sites or AEM Forms? If its forms, please post your query here for quick resolution: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-forms/ct-p/adobe-experience-manager-forms-community Hope it helps!Thanks,Kiran Vedantam.

Hi @jyo2902  Can you share the error that you are seeing while the scheduler is running? Thanks,Kiran Vedantam.

Hi @Marcos_aem  In this use case, you can overlay the error/success message and show your custom message as needed. Hope it helps!Thanks,Kiran Vedantam.

I am seeing this error in author instance and its not supposed to look for the /etc designs in this version of AEM