Different error scenarios faced on pages in AEM as cloud incase any issue with Page / Asset

[raju-komari]

Hi All,

We are seeing below error messages as common for first two scenarios incase any api call issue or jcr node related issues.

'Unexpected error: looks like some issue with our service, We are working hard to bring it online Again".

Scenario -1 

With custom API call where we have dropdown values are coming form API which is getting issue on form-registration page with above message, Post validating the logs we see that getting API call issue & we have fixed API issue.

Scenario - 2

We have json file path configuration in dialog from product-details component and seeing blank page in Author & above default error message in Live page - Production environment.

We have taken this page from production to lower environment and unbale to replicate issue where we should get blank page in author environment, seeing same error from logs .Cannot get DefaultSLingScript: java.lang.Nullpointerexception

That to unable to validate jcr node properties in UAT/STAG/Production sites to do further investigation due to access restriction in AEM as Cloud.

Scanrio3: We have content package of single page with jcr:content/root/ 3 nodes( component nodes) where single component/ node deleted as part of package , we are trying to install this package into AEM as cloud environments and getting OAK error and unable to install package with same page to override 3 components with 2 components as jCR node update by installing package into dev/qa/stag/prod.

Scanrio4: We are trying to update same image in production assets, but not reflecting in live site even we have cleared cache with the help of platform team, but no luck. After raising Adobe Support Ticket, they have cleared the cache to fix the issue after 4 days follow-up, Why we need to depend on Adobe Support team in this case ? because of using AEM as cloud? 

We are clearly seeing that your team creating dependency with your Support team if we are using AEM as cloud. and also seeing different different page behavior from across environment like dev/qa/stag/ ( looks good ) and prod( not working as expected).

I know the process to raise ticket to Adobe Support , but it will take 5-7 days to fix this issue from your side, we could troubleshoot the issues in quicker manner without depend on Adobe Support team if we have access.

Kindly share your comments / suggestions on this cases to fix the issue in quicker manner.

[EstebanBustamante · Accepted solution]

Hi,

I don't understand fully what are your issue due to you posting several issues that are not related to each other, but overall I see you are having issues troubleshooting issues in AEMaaCS. 
My recommendation would be to:

- Take a look at the logs which are available for you to download, you can learn more here: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-.... Particularly in Scenario 2, the logs will point you where the NullPointerException is happening so you can fix that.

- Check the node's properties by using the Cloud Manager Repository Browser: https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/debugging/debugging-a... 

- Check the different options available while debugging issues: https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/debugging/debugging-a... 

Hope this helps

[raju-komari]

Hi @EstebanBustamante

Thank you so much for your update to trouble sheet issues using repository browser console on jcr nodelevel debugging.