Check https://jackrabbit.apache.org/filevault/filter.html to exclude/include paths in filter.xml in META-INF/vault.

You can check Asset published or unpublished through Publish Asset Report:https://experienceleague.adobe.com/docs/experience-manager-learn/assets/advanced/asset-reports.html?lang=en

You can check the dispatcher log to see if the content is fetched from the cache.Also, validate caching rules as well.

Check logs for errors.Also, could you share the AEM version and screenshot of the error?

Servlet : com.day.cq.wcm.core.impl.servlets.SitesExportServlet

You can use the Developer Console: https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/debugging/debugging-aem-as-a-cloud-service/developer-console.html?lang=en#:~:text=AEM%20as%20a%20Cloud%20Service%20provides%20a%20Developer%20Console%20for,has%20it's%20own%20Developer%2...

You can compile your scss to css for aem clientlibs.Refer: https://github.com/eirslett/frontend-maven-plugin

Check https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-restrict-component-editing-and-allowed-only-for-certain/m-p/358938 for limiting editing for page properties.

Validate the AEM cloud version is same in both Non PROD and PROD instance?Try raising adobe ticket along with logs from both instance.

Check https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/authentication/saml-2-0.html?lang=en for SAML 2.0.