Hi @TB3dock, Is this happening at every path where you are trying to create a page or only at a specific path?If only at a specific path, can you give write permissions to the user individually at that path and check?Try checking the permissions for the user by going to the http://localhost:4502/use...

Hi @shelly-goel  Can you please try whitelisting this AEM server in the receiving server to resolve this issue? Thanks,Kiran Vedantam. 

Hi @hs06, Please try using schedulers functionality for this use case. Create a scheduler and delete the user-id by checking if it is existing. You can run the scheduler at your convenience - if the user id is supposed to be deleted in 24 hours after getting created. Thanks,Kiran Vedantam

Did that resolve the issue?

Hi @kgiribabu, The best way to debug this issue is to check if the AEM server is having any network blockers to connect to the SMTP server. Please check with the network admin and try whitelisting the SMTP server. This will resolve the issue. Thanks,Kiran Vedantam.

Hi @senthil86  Whats the log exactly says? Can you share it with us? Also, can you try and replicate in the lower instances - preferably in your local to debug further? Thanks,Kiran Vedantam.

Hi @davidef34326447, You can overlay the core component in your project and create your custom logic on top of it. Use the below example for your use case: https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-wknd-tutorial-develop/project-archetype/custom-component.html?l...

When I click the save button, it is getting saved. This is working fine at page properties level, but not working at metadata level

I have followed the below-mentioned URL and worked on the custom validation on metadata schema. Once the error is shown, the metadata is getting saved even there is an error. Can someone please suggest if there is something missing?https://medium.com/@theopendle/aem-custom-metadata-forms-for-assets-...

Hi @salamswapnil, Is the same issue reproducible when you author the component individually? What does the error.log say? Please share the log for getting more info on the issue. Also, check the parent component itself without adding a sub-component to check if there is any issue in its code. Thanks...