I've built a fairly complex macro, which is being called from a restful service. The macro can't take into consideration all the possible options that might occur on the screens that it passes through - the logic & checks involved would just be too complex. I am handling quite a few, and have success rates over 90%. But that last 10% or so have situations where the macro times out. And I'd like to handle this as well as I can.
Our restful service returns a 500 Internal Server error upon timeout. Is one option to try to catch this in the integration object, or restful service java code?
Or is there a way to work a macro to introduce a transient "in case of timeout, do this" exit point? (considering that there are already a number of transient screens involved in the macro)
I am hoping to introduce some sort of "catch-all" that can return back enough information to the user so that they can make a decision based on the error or the contents of the last screen, or something like that. (we are extracting a before & after view of each screen for debugging, but a timeout doesn't let us return anything nice through the restful service)