Update docs (HTTP Request retry)

docs/custom-actions/action-types.md

@@ -210,6 +210,19 @@ The response of the request is stored in a series of variable names prefixed wit
 * `$your_prefix.url$` - the URL the request was sent to
 * `$your_prefix.error$` - if the request resulted in an error, it's stored in this variable.
 
+#### Retry
+
+When checked, this option will cause the HTTP to be retried in case of a network error, timeout, or related issue.
+
+Per default, there are 3 retries (4 requests total) with 1 second delay between each retry.
+
+!!! note
+    As Webhook.site URLs have a maximum of 30 seconds to respond, it's best to use a low delay and retry number that stays under 30 seconds total. Otherwise there's a risk the actions won't complete. Alternatively, you can mark the HTTP Request action as [Queued](/custom-actions.html#queued-actions), which has a timeout of 120 seconds.
+
+If a status code is specified, the request will also be retried when the response status doesn't match the specified status code. The character `*` can be used as wildcard, e.g. `20*` will match any status status code between 200-209.
+
+Each retry attempt will add an extra line of output.
+
 ### Send Email
 
 This will send a email with variable contents from the Webhook.site cloud. Variables extracted previously can be used.

docs/news.markdown

@@ -22,6 +22,11 @@ Subscribe below to receive updates about improvements and new features on Webhoo
 </form>
 </div>
 
+## 25 April 2024
+
+* Retry functionality has been added to the HTTP Request action. Per default, Webhook.site will retry a HTTP request in case of timeouts. A status code can be specified as a retry condition. [More info here](/custom-actions/action-types.html#retry)
+* The timeout of Queued actions have been increased to 120 seconds. This means that a series of queued actions have 120 seconds to complete.
+
 ## 24 April 2024
 
 * For incoming emails, in addition to text and raw content, HTML content is now shown separately.