Added hint box linking to DLQ feature in scheduling and retries doc. Applies to #2207.

eschabell · eschabell · commit 43fa2e8eba7d · 2025-11-26T09:56:41.000+01:00
Signed-off-by: Eric D. Schabell &lt;eric@schabell.org&gt;
diff --git a/administration/scheduling-and-retries.md b/administration/scheduling-and-retries.md
@@ -95,6 +95,10 @@ The scheduler provides a configuration option called `Retry_Limit`, which can be
 | `Retry_Limit` | `no_limits` or `False` | When set there no limit for the number of retries that the scheduler can do. |
 | `Retry_Limit` | `no_retries` | When set, retries are disabled and scheduler doesn't try to send data to the destination if it failed the first time. |
 
+{% hint style="info" %}
+When a chunk exhausts all retry attempts or retries are disabled, the data is discarded by default. To preserve rejected data for later analysis, enable the [Dead Letter Queue (DLQ)](buffering-and-storage.md#dead-letter-queue-dlq) feature by setting `storage.keep.rejected` to `on` in the Service section.
+{% endhint %}
+
 ### Retry example
 
 The following example configures two outputs, where the HTTP plugin has an unlimited number of retries, and the Elasticsearch plugin have a limit of `5` retries:
