# Handling xmlrpc fault

**URL:** <https://forum.universal-robots.com/t/handling-xmlrpc-fault/190>\
**Category:** URScript\
**Created:** [August 22, 2016, 6:09pm UTC](https://forum.universal-robots.com/t/handling-xmlrpc-fault/190 "2016-08-22T18:09:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon93510157](https://avatars.discourse-cdn.com/v4/letter/a/77aa72/32.png) [@anon93510157](https://forum.universal-robots.com/u/anon93510157)\
**Post date:** [August 22, 2016, 6:09pm UTC](https://forum.universal-robots.com/t/handling-xmlrpc-fault/190/1 "2016-08-22T18:09:57Z")

</div>

Is it possible to handle a xmlrpc call that returned a fault. For the moment, when a fault occurs, the program stops. I would like my programs to be able to react to those errors.

---

<div class="post-metadata">

**Author:** ![jbm](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/jbm/32/614_2.png) [@jbm](https://forum.universal-robots.com/u/jbm)\
**Post date:** [August 23, 2016, 6:58am UTC](https://forum.universal-robots.com/t/handling-xmlrpc-fault/190/2 "2016-08-23T06:58:06Z")

</div>

XML-RPC calls are considered just an extension of the available script commands.  
As a script code is malfunctioning, e.g. like a syntax error for other script codes, this will cause the program to halt.

What would in your opinion be an alternative to the broken call message?  
A popup, or some blank return that could be used in logic?

---

<div class="post-metadata">

**Author:** ![anon93510157](https://avatars.discourse-cdn.com/v4/letter/a/77aa72/32.png) [@anon93510157](https://forum.universal-robots.com/u/anon93510157)\
**Post date:** [August 23, 2016, 12:02pm UTC](https://forum.universal-robots.com/t/handling-xmlrpc-fault/190/3 "2016-08-23T12:02:55Z")

</div>

I think there could be a kind of try catch mechanism that would let the programmer decide what to do in case of a fault returned by a xmlrpc call. If the xmlrpc call has no exception handler, we can display the broken call message, otherwise, we can catch the fault in the program and react based on the fault code.

---

<div class="post-metadata">

**Author:** ![mbush](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/mbush/32/76_2.png) [@mbush](https://forum.universal-robots.com/u/mbush)\
**Post date:** [August 28, 2016, 3:35pm UTC](https://forum.universal-robots.com/t/handling-xmlrpc-fault/190/4 "2016-08-28T15:35:35Z")

</div>

I second that, also, it would be helpful if we could modify the error messages that pop up when there is an issue as they are not very useful for end users who just see an error but have no clue what it means.