In XAML, I put a Try Catch around the entire workflow, and use the Try block inside it for the normal processing.
There is a reason for this: I want to be able to identify the error details no matter where an error occurs. (Error logs are saved to a specified location.)
It worked fine in Studio, but in StudioX it doesn’t seem to go to the Catch block properly.
Is there any special setting I need to configure?
Thank you in advance. Here’s an illustration.
Hello,
This is probably because GlobalExceptionHandler is enabled in StudioX, so the exception is caught there first.
You can either open it in Studio and remove the GlobalHandler settings, or, although this is unofficial, edit the contents of project.json using a text editor or similar.
Yoichi, thank you as always for your help.
The version is Studiox 2023.4.4.
I also deleted the exceptionHandlerWorkflow line from project.json, but it still doesn’t work.
I’ve created a simple sample.
It uses the Yahoo! route search website.
The steps are: leave the “Departure” field blank, enter “Otemachi” in the “Arrival” field, and click the search button.
Since “Departure” is blank, the UI for the next action cannot be found, so I would expect an error and for execution to proceed to Catch, but instead an execution error is displayed.
I apologize for the trouble, and thank you in advance for your help.
try_test.zip (452.8 KB)
Dear Yoichi,
As you pointed out, changing it to Cathes System.Exception resolved the issue.
I hadn’t checked the settings carefully. I sincerely apologize.
Also, it would not work correctly unless I deleted the exceptionHandlerWorkflow line from project.json.
Could this depend on the version?
I’ll be sure to keep this in mind when creating these in the future.
Thank you very much.
In the content linked in the post above, it says:
Try opening project.json in Notepad or another text editor and deleting the exceptionHandelerWorkflow line.
So I believe that’s what you should do. (The version is irrelevant, and StudioX alone doesn’t provide a way to disable GlobalHandler in the first place. By the way, directly editing project.json is an unofficial method, so please bear that in mind.)