Hello, I don’t seem to be able to open the invoke code activity anymore, which seems to have happened after it’s UI update. Do I have to now write the code outside of the activity… notepad.. and then paste it.. this seems like a bug/downgrade?
I see a post here: UiPath 26.0.197 July Community Release - #3 by autodev , which makes it seem like it works on compact version.. but did we make sure it still works on non-compact studio versions?
Yes, I have this issue as well, after updating the System package to 26.6.1 on Studio 2026.0.190. It is supposed to now be a more interactive editor, but I have not had such luck. I’m not sure if I have to upgrade my Studio version, but this is what prompted my question on the other thread. Your best bet right now is to use Notepad/Notepad++/VSCode to do your editing and then copy and paste into your Invoke Code.
Whilst not a direct answer to this bug, perhaps see this as an opportunity to migrate to Coded Workflows/Source files.
Invoke code is far inferior to do such a task compared to those.
Also annoying to do, but you could downgrade Studio to an LTS version if this really bothers you and they’ll perhaps fix it before it gets to you. Might not be ideal cause you do lose some cool features in the STS like coding agents or extensions that arent fully implemented in LTS yet.
@autodev , for this case specifically, my recommendation would be to upgrade to the latest Studio STS version which is 26.0.197.
@David_Hernandez2 what version Studio are you currently using?
2026.0.189 STS, we could upgrade our studio, just requires approval on our end. If we are able to upgrade, I will let you know if this fixes the issue.
Isn’t a fix being that you have to upgrade to the latest STS version sort of bad official advice?
Why is that bad advice?
Its the short term support version, thats how the latest features are released. Its not unreasonable to say that changes are not forwards compatible.
If you are on the LTS release you can avoid stuff like this, but also need to keep on the supported dependencies.
You are asking for a unicorn if you want to have changes available like this, but for them to also be forwards compatible with older studio versions. I dont see it as bad advice.
It is a bug though. It is in fact not intended to display like that. And not anywhere does it say the new studio version is a dependency.
And considering how bug-riddled the average STS version is, yes, I would consider it bad advice.
Why not hold UiPath as accountable as the paying customers? At least for some better release notes and documentation.
That was never mentioned in the July 2026 release forum post, the release notes, nor as a requirement when upgrading the package in Studio. It was only mentioned that if you want the new editor, upgrade to 26.6.1. If you can, please pass on this restriction to the documentation team so they can document it publicly.
Additionally, 26.0.197 is not available through the enterprise installation link (https://download.uipath.com/UiPathStudioCloud.msi). The latest there is 26.0.194. Without downloading the Community version, how else am I supposed to download 26.0.197?
My counter to this is the STS version is exactly that. Short term support, its expected to be auto updated every time any new release is done.
LTS is the stable version you get when you dont want such issues.
Its tricky, cause the LTS can feel extremely slow to come out, meaning you want to use the STS, but it comes with this trade off, if you are using the STS, expect to be always upgrading to the latest patch.
It doesn’t have to be auto-updated, it should be updated as needed. I’m not asking for longer support on my 2026.0.190, but the release notes should at least state that, in addition to updating the System activities package to 26.6.1 to receive the updated editor, that Studio also needs to be upgraded. This has been done in the past, with many activities packages requiring at least Studio 2023.4 to run. LTS is on a similar cadence release as STS, with a release every two to four weeks, if you look at the release notes’ dates.
No argument on the release notes having more detail, but it is my understanding that STS is intended to have auto updates. I’m mostly arguing however that requiring a studio version upgrade, and a package upgrade, isnt unreasonable. Agree better documentation can help.
You are debating about stuff, that does not matter in this context.
The issue also appears in the LTS version, as it is package related, like @edevries already showed in his post above. So you have to downgrade the activitites to come around
Yeah, I agree that the package upgrade seems to be the related factor. My comment was related to the original complaint that seemed to suggest a studio update caused it.
My point stands though.
If you expect an older, LTS version of Studio to work with all the latest packages, you are asking for something unreasonable.
If you are asking for the STS version to never have bugs, then you arent appreciating the point of that version, which is to push out the latest features and have short term support before they make it into the stable branch.
The important takeaway I think from this was the release notes didnt point out the dependency on a later version of studio, and the package details in the package manager often don’t tell you.
It would be good to be able to see that a new System Activities pack requires a minimum Studio version, which was missing here.
I have gone through the above conversation and tried below to provide a response in simple words.
This issue happens because a newer package (like System Activities) sometimes needs a newer version of Studio to work properly. If your Studio is older but the package is new, things can break.
So for now, the safest fix won’t be to just update to the latest package version blindly. Check if it needs a newer Studio version first. UiPath doesn’t clearly shows the “minimum Studio version required” info in the Package Manager, which create issues with the activity usage.
If you’re on LTS, try to avoid installing the very latest package versions unless you’re also ready to upgrade Studio. That mismatch is usually what causes these errors.
Also, quick note for anyone confused about LTS vs STS:
Yes, this looks like a compatibility issue between the newer System Activities package and the Studio version. The new Invoke Code editor requires the newer Studio version. If you are using an older Studio version, try upgrading to the latest STS version or use a compatible System Activities package version. So it’s not necessary to write the code separately in Notepad.
