API Action Properties Pass Errors Bug

[baub]

Wappler Version : 4.6.3
Operating System : Windows 10
Server Model: asp Classic
Database Type: M$ SQL
Hosting Type: Private Server

I had a series of pages that stopped working that were using API calls to grab some data. Everything was working as it should be got call from client this morning that it wasn’t. After some research I realized that the pass errors check was choosen. I turned that off and all started working as it should. Now I don’t know how long this has been going on. But guessing there might be a glitch in wappler that is reversing the state somehow?

[Apple]

If one of the API request fails with “Pass errors” checkbox enabled, the whole script stops. Disabling such checkbox causes the script to continue even in the event of an API request error

So, most likely, one of your API requests is failing

Repeat loop api call returning 404

API Action failures don’t throw an Exception, hence Try/Catch doesn’t work There’s a feature request for this issue: If the loop stops after a 404 error, you need to untick the “Pass errors” checkbox on the API Action - this is because once an “error” happens, such API response is proxied to the actual response of your Wappler app (due to the “Pass errors” option, which is ticked by default) To verify if an error occured with that checkbox unticked, one would need to check the status code…

[baub]

My point is I didn’t check the “pass errors” checkbox to start with? And if I uncheck it then the script works

[Apple]

@baub

My point is I didn’t check the “pass errors” checkbox to start with?

Wappler’s default is to have such box checked. I’ve made a request for the Wappler team to change this behaviour and leave it unchecked by default:

API Action Throw Error Option

I’m bumping this topic and take the opportunity to suggest “Pass Error” checkbox should be off by default “Pass Error” makes API errors difficult to diagnose. I was getting a “502 Bad Gateway” error and thought my web server was broken - turns out it was the API Action that was receiving that from the remote API The suggested “Throw Error” seems more appropriate to be checked on by default

@baub

And if I uncheck it then the script works

The script may work, but e.g.: repeat’s may not have any data to repeat coming from a failed API request. Are you sure the script is processing all data as intended?

[baub]

Positive. All its doing is grabbing a token. And if the “pass errors” is unchecked it grabs the token and works no problem. the rest of the server connect scripts won’t work without the token. and like I said before, I didn’t check the pass errors box, and all the scripts that were using that all had them checked. Maybe I’m hallucinating, but maybe the api provider changed something? I’ve have issue resolved just by unchecking it. But still guessing there might be an underlying issue, because I am always good about stumbling on to them. LOL

[Apple]

That’s a pretty odd thing! Can you tick the checkbox again and post here the error you get? Supposedly, that error would come from the failed API request

Also post the response headers (open your browser’s developer tools -> network)

I can only guess the API started answering an HTTP error code different than 200 (OK) by their developer’s mistake, let’s see if that’s the case. Or, there’s indeed a Wappler bug

[baub]

well now I’m not getting the error. Maybe it was an API provider issue? I will look at it a bit closer and do some more testing and get back to you.