Hi @BostjanR ,
Thanks for reaching out.
It's good to hear that you were able to resolve the issue by editing the registry key for the GSA client forwarding profile.
Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others", I'll repost your solution in case you'd like to "Accept" the answer.
Regarding your question about where the GSA client loaded the wrong forwarding profile from after it was reinstalled,
After initial deletion of application directly from Enterprise blade cannot delete the app immediately and resulted in an orphaned app in the DB. This could have caused the GSA client to load the wrong profile even after it was reinstalled. This is a known issue, and our team is looking into this.
To prevent this from happening in the future, you can try deleting the forwarding profile when you delete an application. This should ensure that the GSA client loads the correct forwarding profile when the application is reinstalled.
Hope this will help.
Thanks,
Shweta
Please remember to "Accept Answer" if answer helped you.