Invoke Code bug?

m365

First when I place Invode Code on the editor, I get the button to Open Editor. I enter my code and run it, it works fine. When I go back to the code to change/tweak it, my changes do not get saved - it automatically reverts back to the same window.

Version: 1.2.41.0, Windows 10

This would be a bug right?

m365

I removed the wsurl value from the settings.json file, it seems to be operating correctly.

Allan Zimmermann

That is definitely a bug. But I can not reproduce it here, can you give more info ?
What language did you choose, can you share what you had in the Code Editor, when this started to happen ?

m365

What language did you choose
I just have english installed.

PS C:\Users\MMM> reg query "hklm\system\controlset001\control\nls\language" /v Installlanguage

HKEY_LOCAL_MACHINE\system\controlset001\control\nls\language
    Installlanguage    REG_SZ    0409
	
PS C:\Users\MMM> sudo dism /online /get-intl

Deployment Image Servicing and Management tool
Version: 10.0.18362.1379

Image Version: 10.0.18363.1500

Reporting online international settings.

Default system UI language : en-US
System locale : en-US
Default time zone : Eastern Standard Time
Active keyboard(s) : 0409:00000409
Keyboard layered driver : PC/AT Enhanced Keyboard (101/102-Key)

Installed language(s): en-US
  Type : Fully localized language.

PS C:\Users\MMM> systeminfo | findstr /B /C:”System Locale”
System Locale:             en-us;English (United States)

can you share what you had in the Code Editor, when this started to happen ?

Start-Process "C:\Program Files (x86)\<<REDACTED>>\cwin64.exe"  "`"D:\<<REDACTED_PATH>>\2011.ac`""

I had to mask some information from the command.

The reason I used invoke code is because when I tried to do the same thing using StartProcess, i got the below error.

[21:36:54.338][Output] New Workflow failed in 00:00.217
# System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
   at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
   at OpenRPA.Utilities.StartProcess.Execute(CodeActivityContext context)
   at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
   at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)

m365

So I just had the issue happen to me again. It seems to occur if there is an extended period where the application is idle/minimized and then I try to edit the Invoke Code block.

My current workaround when this happens is to close/open the workflow file.