Hi @Dave, that interestingly contradicts what @bryce informed me - ie webhook timed out. My testing showed that 5 seconds was the undocumented constraint and it was an upstream timeout to the webhook destination. I’ve asked that the docu be updated and perhaps a more informative error message.
We’ve talked about the rate before, last June a specific whitelist was created, though it may be useful to check that its still in place for https://r6g4i5ujf9.execute-api.us-west-2.amazonaws.com ? Worth noting that I’m more than happy to list the destination url as because it has some of the world’s best rate limiting and security on it though I appreciate the ‘do no harm’ netcitizen approach Particle has defaulted to for web properties that could easily be taken down by a bot attack like Mirai last October.
You’re right in that it’s an interesting trap for young players though, but I’d hope the wildcard whitelist had been implemented to help them out, ie (https://.execute-api..amazonaws.com)
EDIT: other thread of ESOCKETTIMEDOUT was: What does ESOCKETTIMEDOUT mean? I created a more visible thread as I realised someone in the community that wasn’t watching this old thread may know.