I have a primary workflow that has been running fine for many months. I recently updated the packages (UiAutomation and System) and an unexpected UI automation error appeared where the workflow no longer could find the element on the page. I reassigned it in the Click activity and recompiled and immediately got the error above CS0029 which appears to be a C# compiler error. After a day of trying to resolve by examining Invoke arguments I just went through and deleted all the Invokes and recreated them in order to pick the arguments from the Intelliprompt. This worked, but today I encountered the original issue of the workflow not being able to locate and element. I reassigned it and recompiled and I am back to where I started. Anyone know what is causing this issue?
- When developed what are the versions of studio and package?
- what are the new versions?
- Also is it happening on any specific activity
cheers
Studio is 2025.10.1, UiAutomation is 25.10.6, System is 25.10.3
This is for one out of 3 questions
if the upgrade is from 23.10 or older then the issue might be the compatibility as there are many changes also some screenshots can help here
cehers
I have disabled one of the big workflows which is invoked three times in different place one level down and it compiles. Previously I deleted all the Invokes and recreated them using the picker for the arguments. I could delete and recreate the Invoke that I have disabled, but be better if I understood what is causing the problem as it appears inconsistent.
I will upgrade the packages to the latest (not preview versions).
The package upgrade has not resolved it. If I enable this one workflow it fails. I will delete and recreate and see if that resolves it, but there may be issues further down. Yesterday I had to delete all the Invokes below this one as well.
Delete and recompile didnât work, so assume the issue is buried further down, as the top level arguments are repicked and valid (no missing or misconfigured errors). I really need a diagnostic method to isolate the issue, but the compile error is not helpful in pointing to where the issue is other than providing the error code and a line number which I assume is the C# listing?
Open the xaml in notepad++ and try to go to the line mentioned in error may be that can point to the issue
Can you uplod a full screenshot of the error and give a description of what is happenicng in xaml
Cheers
Sorry I had to head off for a meeting. Will have a look now.
The line in the error is I think the C# compilation file not the xaml. The xaml has just under 9,000 lines. The full error listing is:
The assembly compilation returned the following errors:
- (1,4172): error CS0029: Cannot implicitly convert type âSystem.Activities.InArgumentâ to âSystem.Activities.InOutArgumentâ
- (1,4400): error CS0029: Cannot implicitly convert type âSystem.Activities.InArgumentâ to âSystem.Activities.InOutArgumentâ
- (1,4632): error CS0029: Cannot implicitly convert type âSystem.Activities.InArgumentâ to âSystem.Activities.InOutArgumentâ
- (1,4858): error CS0029: Cannot implicitly convert type âSystem.Activities.InArgumentâ to âSystem.Activities.InOutArgumentâ
- (1,5085): error CS0029: Cannot implicitly convert type âSystem.Activities.InArgumentâ to âSystem.Activities.InOutArgumentâ
- (1,5444): error CS0029: Cannot implicitly convert type âSystem.Activities.InArgumentâ to âSystem.Activities.InOutArgumentâ
- (1,5677): error CS0029: Cannot implicitly convert type âSystem.Activities.InArgumentâ to âSystem.Activities.InOutArgumentâ
Its just completed the assembly compilation, but gives no specific pointers to what in the compilation failed other than the CS20029 and cannot implicitly convert type.
Sorry that c# error should have been CS0029
Given I havenât had to visit this workflow for a while, I am wondering whether I have missed an announcement that says older workflows need to be completely rebuilt from scratch in the c# version? Have I?
Thats one reason askign for what is the previous version as there has been many changes
also as per error looks like recreating argument should fix
also when you do that go to every invoke use refresh argument to reflect latest
also to check you can delete all the folders stating with . (dot) like .locals etc they would be recreated..take a backup
cheers
I gave up, so given the workflow isnât transaction driven, so technically doesnât need a state machine, I am converting it to a linear workflow to get around the arguments issue. A massive consolidated workflow! The primary issue now is that the Studio editor canât handle the size when it does its synchronous error checking. I think I can switch this off so that may help.
Eventually I found out what the underlying issue was. It is apparently a long standing and known bug which means if you had a Windows Legacy project and you converted it and you are now using the latest editions of the Studio designer, Studio declares arguments with defaults as In arguments in the xaml even though they are I/O in the designer. You canât resolve it from the Studio editor. You need to modify the xaml. All working now. So no need to convert to a linear sequence, but itâs a better structure for this problem and overdue revision!
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.