I am experiencing an issue where I am using a Start Job activity in my workflow yet every time I reopen this workflow the argument inputs I have inputted keep getting wiped out…is anyone else experiencing this issue?
example:
Please spwcify the studio and package versions…
Did you happen to try with a different system package version?
Cheers
Nope, but it doesn’t surprise me.
These new dynamic activities are super buggy, I have so many support tickets to make for them.
I have a similar issue with the Outlook Send Mail Integration, that one doesn’t remove the argument entirely though, it just removes part of it. Its super annoying and only happens when you open the workflow.
1 Like
I recorded a video demonstrating it live (hopefully it will play).
Its trying to be helpful and ‘fix’ some text but ends up just wiping it out and ruining an expression.
Similar things might be happening with the Job where it tries to help ‘correct’ an argument, hits an error and then wipes out the value. Nasty bugs, I’d prefer it if they were abit less keen to try to correct my code and instead gave me a choice or a suggestion I could choose to refuse.
2 Likes
Studio version 2023.4.1 and system activities package is 23.10.2 - do you know if there is a known bug in the system package that has been addressed in particular versions?
one suggestion here always better to maintain system packages equal or less than studio version but not more
cheers
For sure if you go to a lower version you can get rid of this issue, if you find one old enough so they don’t use the ‘dynamic activities’ you should be able to avoid this issue.
Try going back to a 22.10 version and see if the layout is more static.
Its not related the Studio version afaik @Anil_G the activies package releases and studio releases are not neccessary connected.
Most of the cases system packages are upgrades inline with studio…I agree with you there is no relational rule, but most of the times we saw when system pacakges are higher there is an issue. So gave the same
cheers
Yeah, in general its not bad advice, but you can definitely use later packages than the version you are on.
In this case I am pretty sure its related to the dynamic activity stuff recalcing what the input arguments for the job are, trying to refresh the display of the activity and destroying the existing value as it goes. You see a similar thing in my video where the dynamic activity is messing with values and removing them.
The dynamic activities in general are buggy.
2 Likes
even when upgrading to latest version of studio fields still getting wiped out when activity reloads - my workaround has been to isolate the activity within it’s own workflow file and pass the same arguments to it so that way when opening main workflow file the start job activity is not getting reloaded and wiping out the arguments.
1 Like
Just to loop back on this topic, and hopefully close it out.
I’ve just tested the behaviour above.
For Start Job activity, it reproduced on System 23.10.2, but no longer reproduces on System 23.10.6 (latest patch), as well as the latest System 24.3.1. So that issue is fixed 
For the Outlook 365 Send Mail activity, it still reproduces for me on the latest UiPath.MicrosoftOffice365.Activities 2.6.20-preview. I’ll make sure this reaches our team, it looks super frustrating.
I see you going over a bunch of my old posts 
I did my due dilligence and did report this through the customer portal back in December
The case number is Case #:02317985 and it got turned into an internal bug as SPM-4478 so if you want to see where it is in the development pipeline that should give you some clues.
I’d be interested to know if it got stuck/lost along the way if its still not being worked on and how we can work better to get the bugs through in the future so feel free to PM me if you wish to on this topic.
1 Like
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
pikorpa
prashant1603765
Anil_G
ben.smith
jrdev2