There was a network change made early this afternoon that we rolled back.
–
As to why it would happen to you other times, there could be a number of factors at play and there’s not any user-facing tools for the proxy flag beyond what your browser developer tools would show. That being said, the only time you should really need the proxy flag is if the server you are calling has strict CORS limitations (like IFTTT). If your server allows calls from other websites, you could drop the proxy flag.
Alternatively, you could create a SharpTools Rule with an HTTP Trigger which has an HTTP Action to call your endpoint. You could then store the response status and error message from the HTTP Action, accessed from context variables, into another variable. That has the added benefit of logging the response status and error to the rule logs for historical review.
In this example, the server I was calling started responding with a 404 as the endpoint I was calling was only valid for a short period of time before it was deleted.