HTTP request failure in a scene

Until yesterday, one of my scenes retrieving air pollution info from the waqi.info API was working fine. I noticed this morning that it no longer is.
When I test the action in the scene, the error below is displayed (you can’t see it in the screenshot, but the URL is complete, with the token…).
image

Whereas when I access the same URL from my browser, the resulting JSON is displayed correctly.
image

Any idea what I should check?

Check Gladys’ logs, that should give you more information! It’s strange — normally I think the error should appear in the interface.

It works fine for me

In the URL field I use this:

https://api.waqi.info/feed/maville/?token=montoken

Ah, the mysteries of computing: I absolutely didn’t change anything in the scene, and today it’s working again!

1 Like

In my opinion, if you run into a network issue with a timeout just when you send your request, you end up with the error.
By the way @pierre-gilles, is it possible to set up some kind of watchdog in the scenes for HTTP calls? (with 5 retries for example)
I have a request to timeapi.io that works once out of five and I end up with blanks instead of the values :frowning: but when I run the scene several times in a row manually I get a response eventually.

I thought about that a bit yesterday, but in my tests I alternated the same request from the Gladys scene and from my browser, and all attempts from Gladys failed while all those from the browser were OK.

But anyway, it’s not a big deal, it seemed to be a one-off…