RELATED IDEAS
Support non-OK status-code in xtensions
Currently if a xtension responds with a code other than 2xx the call is considered to be a failure.
However many APIs legitimately return a status-code other than 2xx. For example if you query a service and no results are found, many APIs return 404 - "Not Found". This is a valid response and I would like to react on this response within the workflow. Many times this would result in either creating a new record (if a query returns 404) or updating an existing record (if a query returns 200).
However many APIs legitimately return a status-code other than 2xx. For example if you query a service and no results are found, many APIs return 404 - "Not Found". This is a valid response and I would like to react on this response within the workflow. Many times this would result in either creating a new record (if a query returns 404) or updating an existing record (if a query returns 200).
-
ADMIN RESPONSESep 7, 2022We're reviewing this request internally.
The Error Handing feature is currently under development and will resolve this issue. Changing status to [Already Exists]
I agree, I would like to be able to handle all response types on the custom xtension. Mainly 404's, 500's. In my case both of these values need to send emails out to customers to resubmit a form.