Page 1 of 1

catching unexpected errors

Posted: Wed Sep 22, 2010 9:41 am
by magicsoft
I was just wondering what the situation is regarding unexpected problems during a call process. For instance, what happens if the "result URL" for an outbound call becomes unavailable AFTER it's checked at the start of the call? The call completes, but then PLUM can't post the results. Does this type of unusual thing get logged anywhere? The way I have things set up, I'd have to have some way of knowing that something like that happened, because it would affect my data. I can't think of any other specific examples, but I just wanted to get some idea of what my options are as far as determining any problem that might be happening that wouldn't necessarily be obvious by looking at the call logs or reports themselves. I just want to make sure that I know if anything has gone wrong in the process, so I can do something about it.

Thanks,

Andrew

Re: catching unexpected errors

Posted: Wed Sep 22, 2010 2:52 pm
by support
Hi Andrew,

For the particular situation you are describing, there isn't any way to handle the error gracefully in your code, because it is our outbound system that is making the call to result_url. In other cases, you can always add <catch> handlers to your code that will catch specific events, such as:

Code: Select all

<catch event="error">
    This is a custom error message.
</catch>
You can also add <log> tags throughout your code in order to save custom messages and information in your call logs. In any case, you will have to view your call logs before you can know what really happened.

Regards,
Plum Support