Ok, here is the thing Since you are getting new screen you have to use the Use Application/browser activity every time you see a new screen.
and the reason you are getting that error is for same that the UiPath is unable indicate a new target.
work around is you can use classic activity attach window. (not recommended)
Recommended by UiPath is to use the Use application activity for every new screen.
Remove volatile parts such as title=…, text=…, numeric id, or explicit transaction codes.
4. Test by running the robot and navigating through several screens; no new prompt should appear.
5. Delete any duplicate “Use Application/Browser” cards and nest all UI activities under this single container.
Yes, sometimes it’s necessary to use the “Use Application/Browser” activity for all windows—
but in some cases, it can work without it as well. However, when not using it explicitly for every window, make sure to update the “Use Application/Browser” activity by making it dynamic, especially by adjusting the selector to handle different window titles or instances.
Example:
wnd app=‘chrome.exe’ title=‘Invoice - Google Chrome’
Make it As:
wnd app=‘chrome.exe’ title=‘Invoice’
Its generally more recommended to stick to the Enterprise versions to avoid stability issues that you may get in Community.
Is there a new Community feature you wanted to use that prompted you to upgrade to the latest community version? If it doesnt affect the previous versions a downgrade can solve it for now.