💡  A new input parameter, (defaulted to false obviously,) to REST calls called "ContinueOnError", which causes the rest method to return successfully, but with 3 additional fields (or even a structure) returned with "Success", "HTTPResponseCode" and "TextContent" fields.

📉 Some REST APIs return "failure" HTTP Response Codes for valid responses, such as "404 Not Found" if the record doesn't exist.  (Lets ignore the debate about using 404 for record not found *AND* page not found.)

🕞 In the context, this may not be an a error, but it's going to end up in the generic error handler where you are going to be parsing the text of the error message to try to see what actually went wrong, and possibly displaying a load of technical junk to the user.

📜 Even within a single error code, there could me a range of causes, with the details being in the response as JSON.

🔍 Now obviously, I know you can do all this with code in OnAfterResponse, but you can't set that on a API method level, only on the connection, so you're going to have some pretty ugly code in OnAfterRespose to work out which API of ten calls you made and whether it's really an error.

🎯 I suggest it would be far better to have an option to allow the API call to continue to the next step in the procedure, then check the response to see if it succeeded, and work out if we need to raise an error, retry, or just continue, based on the response.

Edit to add: This doesn't seem like it should be particularly hard to implement.
Edit to also add: Added icons because everyone else uses them