diff --git a/app/vmalert/README.md b/app/vmalert/README.md
index f268cf959f..f5b5d27513 100644
--- a/app/vmalert/README.md
+++ b/app/vmalert/README.md
@@ -650,6 +650,10 @@ may get empty response from datasource and produce empty recording rules or rese
 
 <img alt="vmalert evaluation when data is delayed" src="vmalert_ts_data_delay.gif">
 
+_Please note, by default recently written datapoints to VictoriaMetrics aren't visible for queries up to 30s.
+This behavior is controlled by `--search.latencyOffset` command-line flag on vmselect. Usually, this results into
+a 30s shift for recording rules results._
+
 Try the following recommendations in such cases:
 
 * Always configure group's `evaluationInterval` to be bigger or equal to `scrape_interval` at which metrics 
diff --git a/docs/vmalert.md b/docs/vmalert.md
index 8d6f181597..cd28c54682 100644
--- a/docs/vmalert.md
+++ b/docs/vmalert.md
@@ -654,6 +654,10 @@ may get empty response from datasource and produce empty recording rules or rese
 
 <img alt="vmalert evaluation when data is delayed" src="vmalert_ts_data_delay.gif">
 
+_Please note, by default recently written datapoints to VictoriaMetrics aren't visible for queries up to 30s.
+This behavior is controlled by `--search.latencyOffset` command-line flag on vmselect. Usually, this results into
+a 30s shift for recording rules results._
+
 Try the following recommendations in such cases:
 
 * Always configure group's `evaluationInterval` to be bigger or equal to `scrape_interval` at which metrics