Issue Summary

Currently, the automation action send web request has a fixed timeout of 30 seconds, returning the following message if the endpoint takes longer than 30 seconds to run:

Web request was sent, but timed out after 30 seconds on the remote host so the result is unknown (but most likely successful).

Sometimes, the endpoint has different timeout settings, such as 60 seconds, depending on its purpose. 

Suggestion

Provide users the ability to change this 30-second timeout value to better accommodate the end user's needs. 

Workaround

You must ensure that the endpoint returns something within the 30-second window; otherwise, the error mentioned above will be thrown.