Handling Exceptions

RE: Handling Exceptions

rodgraham — Mon, 05 Jul 2021 15:44:05 GMT

you're correct it won't. You'd either need to put the failing node in a sub process and put an exception against the call to the sub process. Or depending on your process a timer node that fires if the process hasn't complete in a given time.

RE: Handling Exceptions

dinasaleh — Mon, 05 Jul 2021 14:55:38 GMT

the failed node will pause the process so how could you add an exception to the failing node?

RE: Handling Exceptions

davel001150 — Fri, 01 Mar 2019 13:33:29 GMT

One other thing you might want to consider is the saved values output. This works slightly better than the true / false by giving you the data from the database so that you can also compare against an expected value in the asynch process waiting to see if database write happened.

This would allow you to log database writes that technically happened, but not as they should, where the node completes but the data is somehow wrong.

RE: Handling Exceptions

Josh — Thu, 28 Feb 2019 14:25:45 GMT

Have a pv that is initially set to false, on the output of the node set the pv to true. In a parallel flow, you can check the pv value to determine if the node completed or not.

RE: Handling Exceptions

josuv0001 — Thu, 28 Feb 2019 14:01:34 GMT

Hi Josh. What is the best way to check if the node completed successfully?

Thanks

RE: Handling Exceptions

Jim Schweitzer — Mon, 10 Apr 2017 12:42:40 GMT

@rodgraham unfortunately the smart service exception path doesn't fire in the case where the node breaks. You have to encapsulate it in a subprocess and let the subprocess node throw the exception as Josh describes

RE: Handling Exceptions

Josh — Fri, 07 Apr 2017 12:37:21 GMT

Unfortunately, there isn't a great solution to this problem. What you can do is schedule a timer to start with your write to Data Store Entity node and after one minute check to see if the node completed successfully. If the node completed then you do nothing, but if it did not succeed, you would restart the timer and the write to data store node.

RE: Handling Exceptions

rodgraham — Fri, 07 Apr 2017 12:07:56 GMT

The failing node will get a red line through it and the process should be visible in processes with problems report. The documentation does state that the final retry is logged as an error. Alert would be generated for the failed node. You could add an exception to the failing node to redirect the process down an alternative path if wanted.