I am running a bot in StudioX. When I’m testing and it throws an error, sometimes GlobalHandlerX displays, sometimes it doesn’t. Is there a certain criteria when it will switch to GlobalHandlerX?
Also, once GlobalHandlerX has opened, I can’t see a way to close it and return to the workflow, except by closing StudioX and re-opening it. Is there a way to GlobalHandlerX and return to the workflow?
I see your question hasn’t been responded to. I hope this still helps after a month and a half.
The Expand and Collapse options are to make it easy to navigate through long workflow files. When you put certain sequence(s) of activities within a scope, e.g. Application Scope or Use Excel File, you can use “Collapse” to see only the main blocks of the process and then expand the one you want to work on, etc.
May I ask what is the purpose to try closing that option?
Alternatively, if you’re looking for a close button (X) to close the GlobalHandlerX file, StudioX is designed to run only one file - Main.xaml to keep things easy.
The opening of GlobalHandlerX during testing may be a bug (though someone from the mod team could confirm it) @loginerror
I am having the same issue. I am running a program and it is randomly opening the GlobalHandlerX and there is no way to close it. I want to get back to my Main project to fix the error, but I cannot do that without completely closing the program and opening it back up again.
Would it be possible to share with us some repro steps on how to trigger this, as well as the StudioX version you are using. Could you maybe provide a sample project that causes this issue for you?
This occurs when I choose “run to this activity” and I have an error occur occur StudioXBootcamp1.7z (690.3 KB)
. You wait for the timeout associated with the error, it goes to the GlobalHandler and doesn’t return to main nor does there seem to be an easy way to select main.
I am currently using Enterprise 21.10.3.
In the attached project try run to this activity to the Outlook activity. It fails, when you notice it stops wait and see what happens.
@Ken_Day
I gladly welcome you to UiPath Community Forums
In your project, it seems there is a problem when creating a new sheet, due to the character limit in the name (31 letters or less)
One of the vendor names is “SAN MIGUEL FOODS ,INC_2022-01-08” which is 33 characters long, and the program fails to create sheet.
Is this the problem you’ve been facing?
Log:
UiPath.Excel.ExcelException: You typed an invalid name for a sheet or chart. Make sure that:
• The name that you type does not exceed 31 characters.
• The name does not contain any of the following characters: : \ / ? * [ or ]
• You did not leave the name blank. ---> System.Runtime.InteropServices.COMException: You typed an invalid name for a sheet or chart. Make sure that:
• The name that you type does not exceed 31 characters.
• The name does not contain any of the following characters: : \ / ? * [ or ]
• You did not leave the name blank.
at Microsoft.Office.Interop.Excel._Worksheet.set_Name(String RHS)
at UiPath.Excel.ExtendedWorkbookApplication.ChangeNewSheetNameAndSetCurrent(Worksheet newSheet, String sheetName)
at CallSite.Target(Closure , CallSite , ExtendedWorkbookApplication , Object , String )
at System.Dynamic.UpdateDelegates.UpdateAndExecuteVoid3[T0,T1,T2](CallSite site, T0 arg0, T1 arg1, T2 arg2)
at CallSite.Target(Closure , CallSite , ExtendedWorkbookApplication , Object , String )
at UiPath.Excel.ExtendedWorkbookApplication.InsertInternal(String sheetName, String insertBefore, String insertAfter, Int32 position)
at UiPath.Excel.ExtendedWorkbookApplication.<>c__DisplayClass76_0.<InsertSheet>b__0()
at UiPath.Excel.ExcelContextHelper.Execute(Action action, ExcelContext context, Object[] contextParams)
--- End of inner exception stack trace ---
at UiPath.Excel.ExcelContextHelper.Execute(Action action, ExcelContext context, Object[] contextParams)
at UiPath.Excel.ExtendedWorkbookApplication.InsertSheet(String sheetName, String insertBefore, String insertAfter, Int32 position)
at UiPath.Excel.Activities.Business.InsertSheetX.<>c__DisplayClass12_0.<ExecuteAsync>b__0()
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at UiPath.Excel.Activities.Business.InsertSheetX.<ExecuteAsync>d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at UiPath.Shared.Activities.AsyncTaskCodeActivityImplementation.EndExecute(AsyncCodeActivityContext context, IAsyncResult result)
at UiPath.Shared.Activities.AsyncTaskCodeActivity.EndExecute(AsyncCodeActivityContext context, IAsyncResult result)
at System.Activities.AsyncCodeActivity.System.Activities.IAsyncCodeActivity.FinishExecution(AsyncCodeActivityContext context, IAsyncResult result)
at System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncCodeActivityWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)
Hello,
I’m also facing the same issue. Might be a bit late, but sharing the only workaround I could think of in case it helps anyone in the future.: it seems like the GlobalHandlerX template comes on screen only if you execute from a certain activity onwards. So what I did was to Comment out/Disable/Hide all the previous activities, and Run the whole process from the beginiing. A bit tacky, but well, it’s practical.