Are you referring to initiator of the workflow user if that’s the case then please refer to https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/is-it-possible-to-get-the-current-user-in-the-workflow/m-p/446998 current user can be found from session object  session.getUserID(); ...

type= cq:Page is not required for the full text for your use case as this property is associated with the page node only. For your use case you can use type=nt:unstructured filter for your search query  

No that should not happen. Once you create/update the user permission it’s get stored on aem repository. Restarting of aem shouldn’t reset the permissions. I am hoping you are having a persistent/ permanent volume or memory assigned to your server. If your custom package installation is doing the re...

Normally those connections are on author only like target and launch integration. For the JWT to oauth migration it depends how your existing setup is and need to be migrated for all. If currently you don’t have any JWT integration with publisher then you don’t need to do anything with publisher. ho...

It doesn’t seems to be OOTB groups as i don’t see this group on my side in admin console user groups

You need to check more entry in logs. It’s actually failing during compilation so it seems it has something to do with your code abd log will give you more insights on this. What about this class ? Have you defined it properly? HeaderModel

From the log it appears the request url is not properly read as it’s making a request to / with no path in it. on the dispatcher as you can see below entry on the log   Mon Jul 15 10:17:24 2024] [D] [pid 17840] checking [/][Mon Jul 15 10:17:24 2024] [D] [pid 17840] request URL has no extension: /[Mo...

From tagging gui you can’t create a localized string for description. However you can try leveraging i18N for this. I have used it for component and Tag title but not for description. follow this for reference. https://www.nextrow.com/blog/adobe-experience-manager/usecase-il8n-converting-components-...

Open an Adobe ticket for this it seems userGroupsSync job is failing.

The answer is no. You need to only update on aem for project2 as this project only requires those configuration in aem. All other project that you have in developer console is used to access via api endpoint and no configuration is present in aem for those so no need to make any changes there.