Try to cross check once if the osgi config is deployed properly using developer console.Also, it could simply be a cache issue. Please try to hit the entire URL directly with some query param. www.yourdomain.com/etc.clientlibs/your-clietnlib.min.js?q=x 

Since you mentioned that you are using it in headful approach, you need to make sure that GTM libraries are actually included on your AEM page (and not just in index.html. I assume index.html might just be used for local development). You can once cross check in the network tab on publish instance i...

I would still suspect that you do not have enough rights to create the technical account. An IMS org system admin can create a technical account. Check this https://experienceleague.adobe.com/en/docs/experience-manager-learn/getting-started-with-aem-headless/authentication/service-credentials#create...

It seems some function binding is taking place to your console.log by the time your DOM gets ready. You should be able to double click your f () {{native code}} during debugging and it should ideally take you to the file where new function is defined and can check within your team to the person resp...

This shows OakState0001 which would mean multiple sessions working on the same node which is why it might have failed sometime.  Following threads might help :https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-assets/gettig-oakstate0001-unresolved-conflicts-error-on-asset-impo...

I tried checking where exactly they are including this clientlib but couldn't find anything other than SystemNotificationsImpl.java So, it seems they are including it from this OSGI component from the backend and not in the traditional way that you would think, in which case trying to include using ...

You can try to check the logs for the cases when it doesn't work. It might be the case, that the asset might already be getting processed by some other workflow when you try to perform the actions in which case, it might not be getting processed properly.

Is this happening after some upgrade ? And is it happening on all the pages or any specific ones ? You can try to uninstall the core component package once and try to reinstall to remove any corrupt files.

if your console.log("99") statement is executing without any errors, then I don't think it could be a loading order issue, otherwise you might have seen some error like $ is not defined.Based on whatever inputs you have provided, I frankly don't see any issue on why it will not work. Few things I ca...

Could you also please check the response for the API call which I mentioned i.e  /bin/wcm/experiencefragments/verifyreferences.json Also check if there are any cyclic references as mentioned on this thread https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/getting-unknown-vali...