summaryrefslogtreecommitdiff
path: root/content/docs/configuration/retry.md
diff options
context:
space:
mode:
authorPhilipp Tanlak <philipp.tanlak@gmail.com>2025-11-24 20:54:57 +0100
committerPhilipp Tanlak <philipp.tanlak@gmail.com>2025-11-24 20:57:48 +0100
commitb1e2c8fd5cb5dfa46bc440a12eafaf56cd844b1c (patch)
tree49d360fd6cbc6a2754efe93524ac47ff0fbe0f7d /content/docs/configuration/retry.md
Docs
Diffstat (limited to 'content/docs/configuration/retry.md')
-rw-r--r--content/docs/configuration/retry.md26
1 files changed, 26 insertions, 0 deletions
diff --git a/content/docs/configuration/retry.md b/content/docs/configuration/retry.md
new file mode 100644
index 0000000..cf00698
--- /dev/null
+++ b/content/docs/configuration/retry.md
@@ -0,0 +1,26 @@
+---
+title: 'Retry'
+weight: 6
+---
+
+The retry feature allows the scraper to automatically retry failed requests. This is particularly useful when dealing with unstable networks or servers that occasionally return error status codes.
+
+The retry feature is automatically enabled and will retry requests that return the following HTTP status codes:
+
+- 403 Forbidden
+- 408 Request Timeout
+- 425 Too Early
+- 429 Too Many Requests
+- 500 Internal Server Error
+- 502 Bad Gateway
+- 503 Service Unavailable
+- 504 Gateway Timeout
+
+### Retry Delays
+
+After a failed request, the scraper will wait for a certain amount of time before retrying the request. The delay increases with each consecutive failed attempt, according to the following schedule:
+
+- 1st retry: 1 second delay
+- 2nd retry: 2 seconds delay
+- 3rd retry: 5 seconds delay
+- 4th retry: 10 seconds delay