Adding some useful info about a gap filling limitation

src/content/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-nrql-alert-conditions.mdx

@@ -714,6 +714,12 @@ Gap filling lets you customize the values to use when your signals don't have an
 * **Custom static value**: Choose this if you'd like to insert a custom static value into the empty aggregation windows before they're evaluated. This option has an additional, required parameter of `fillValue` (as named in the API) that specifies what static value should be used. This defaults to `0`.
 * **Last known value**: This option inserts the last seen value before evaluation occurs. We maintain the state of the last seen value for 2 hours.
 
+<Callout variant="tip">
+  The alerts system fills gaps in actively reported signals. This signal history is dropped after 2 hours of inactivity. For gap filling, data points received after this period of inactivity are treated as new signals.
+
+  To learn more about signal loss, gap filling, and how to request access to these features, see [this announcement](https://discuss.newrelic.com/t/announcing-new-relic-one-streaming-alerts-for-nrql-conditions/115361).
+</Callout>
+
 Options for editing data gap settings:
 
 * In the NRQL conditions UI, go to **Condition settings** > **Advanced signal settings** > **fill data gaps with** and choose an option.

src/content/docs/alerts-applied-intelligence/new-relic-alerts/alerts-nerdgraph/nerdgraph-api-loss-signal-gap-filling.mdx

@@ -15,6 +15,8 @@ Loss of signal occurs when New Relic stops receiving data for a while; technical
 Gap filling can help you solve issues caused by lost data points. When gaps are detected between valid data points, we automatically fill those gaps with replacement values, such as the last known values or a static value. Gap filling can prevent alerts from triggering or resolving when they shouldn't.
 
 <Callout variant="tip">
+  The alerts system fills gaps in actively reported signals. This signal history is dropped after 2 hours of inactivity. For gap filling, data points received after this period of inactivity are treated as new signals.
+
   To learn more about signal loss, gap filling, and how to request access to these features, see [this announcement](https://discuss.newrelic.com/t/announcing-new-relic-one-streaming-alerts-for-nrql-conditions/115361).
 </Callout>
 

src/content/docs/alerts-applied-intelligence/new-relic-alerts/get-started/streaming-alerts-key-terms-concepts.mdx

@@ -139,6 +139,12 @@ Gap filling lets you customize the values to use when your signals don't have an
 
 Gaps in streaming data can be caused by network or host issues, a signal may be sparse, or some signals, such as error counts, may only have data when something is wrong. By filling the gaps with known values, the alert evaluation process can process those gaps and determine how they should affect the loss of signal evaluation.
 
+<Callout variant="tip">
+  The alerts system fills gaps in actively reported signals. This signal history is dropped after 2 hours of inactivity. For gap filling, data points received after this period of inactivity are treated as new signals.
+
+  To learn more about signal loss, gap filling, and how to request access to these features, see [this announcement](https://discuss.newrelic.com/t/announcing-new-relic-one-streaming-alerts-for-nrql-conditions/115361).
+</Callout>
+
 ### Aggregation window
 
 In order to make loss of signal detection more effective and to reduce unnecessary notifications, you can customize aggregation windows to the duration that you need.