TeamDesk Knowledge Base & Support

   Home      FAQ      Forum      Idea Exchange      Ask a Question      My Stuff      Help   
Error messages from Call URL
Currenylt when a call URL action hits an error with On Error set to Stop Execution, depending on whether it was called with the user present or from a background trigger it either
- emails the error message to the administrator identifying the trigger, the action and the message. This is good
- displays that same information to the user, which is not good as it is too much irelevant information for a user.

Suggestion: allow different error handling with different error messages depending on whether the user is present or the error occurs in a background trigger

Philipp Matuschka (MMB)
Date Created
9/12/2019 5:44:08 AM
Date Updated
10/8/2019 8:30:55 AM
New Idea
Promoted By
Patricio BustosPhilipp Matuschka (MMB)
Kirill Bondar  Staff  10/8/2019 8:30:55 AM
Before we introduced Stop/Continue Execution switch we stopped on erroneous third-party server response unconditionally and displayed generic error message. We evaluated Error Formula only on successful results. If formula produces NULL, execution continued, non-NULL result is used as an error message. Checking Stop Execution follows this logic exactly.

Now, if Continue Execution is checked both successful and erroneous results are passed to Error Formula for evaluation. There, in addition to examining the response you can use ResponseStatus() function to quickly check whether the call was successful or not. In general ResponseStatus() >= 400 indicates error ( )

For example, the formula below can be used to extract error message from failed TeamDesk REST API call:

If(ResponseStatus()>=400, "TeamDesk REST API responded with: " & Response("$.message"), null)
Back to Search Results