i found a trick to migrate from studio to studioX
open project json an change this tag
“projectProfile”: “Developement”, → “projectProfile”: “Business”,
i got all my reframework robots in studioX with me! and they work differently but they do their job
other trick is if you still has the studio license just copy the main, other workflows are not necessary to copy they will migrate solo.
Then open in studioX a normal project and paste the main copied previously
if you are using over 2025 version UiPath i have seen a problem having more than one workflow, with activity sequenceX, you have to open xaml with notepad and change all ueab:SequenceX to Sequence
this is the error that show up “message”: “Single Excel Process Scope: Failed to initialize workbook handle, no excel process available”
(no excel was use in the workflow but it was the main canvas UiPath.excel.activities.business.sequenceX)
Tell me if you find it too
and lets automated again!
Hi @amy93amanda
nice find, that error makes sense once you look at what SequenceX actually is. Its not just a renamed Sequence, its a StudioX specific activity type that expects to run inside the StudioX runtime host, wich handles things like the implicit Excel application scope differently than regular Studio does. When you flip projectProfile to Business by editing the json directly, the project loads in StudioX but the underlying xaml still points to the SequenceX activity type without the proper runtime wiring behind it, so anything that depends on an implicit scope like Excel breaks because that handle never gets initialized correctly
your fix of converting ueab:SequenceX back to plain Sequence in the xaml makes sense too, regular Sequence doesnt carry any of that implicit host dependency so it just runs like a normal container
worth flagging though, since this is editing the project json and raw xaml by hand its unsupported, so it can break in unpredictable ways on more complex projects, specially ones using StudioX specific implicit scoping like Excel/Outlook/Word cards that rely on that hidden context. For a handful of simple ReFramework robots like yours it makes sense as a workaround, but for anything bigger id be careful trusting it without testing every workflow path after the conversion
curious if you hit the same issue on projects using other implicit scopes besides Excel, that would confirm its the runtime host thing and not something excel specific
The root cause is that StudioX does not fully support some developer-specific activities, especially SequenceX containers introduced by Excel business activities.
Quick Fix:
- Open the
.xaml files in a text editor.
- Replace all instances of
ueab:SequenceX with Sequence.
- Save and reopen the project in StudioX.
If you encounter the error:
"Single Excel Process Scope: Failed to initialize workbook handle, no excel process available"
even when Excel is not used, it is usually because the workflow canvas is still referencing UiPath.Excel.Activities.Business.SequenceX. Replacing SequenceX with a standard Sequence resolves the issue.
Also, changing the projectProfile from "Development" to "Business" in project.json is a handy way to migrate existing projects, including REFramework-based automations, to StudioX. After migration, thoroughly test workflows because some activities may behave differently in the Business profile.