diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown
index 61c609d5450..996454bc2f8 100644
--- a/source/_docs/automation/trigger.markdown
+++ b/source/_docs/automation/trigger.markdown
@@ -292,6 +292,14 @@ automation:
The `for` template(s) will be evaluated when an entity changes as specified.
+
+
+Use of the `for` option will not survive Home Assistant restart or the reload of automations. During restart or reload, automations that were awaiting `for` the trigger to pass, are reset.
+
+If for your use case this is undesired, you could consider using the automation to set an [`input_datetime`](/integrations/input_datetime) to the desired time and then use that [`input_datetime`](/integrations/input_datetime) as an automation trigger to perform the desired actions at the set time.
+
+
+
## State trigger
Fires when the state of any of given entities changes. If only `entity_id` is given, the trigger will fire for all state changes, even if only state attributes change.
@@ -449,6 +457,14 @@ Use quotes around your values for `from` and `to` to avoid the YAML parser from
+
+
+Use of the `for` option will not survive Home Assistant restart or the reload of automations. During restart or reload, automations that were awaiting `for` the trigger to pass, are reset.
+
+If for your use case this is undesired, you could consider using the automation to set an [`input_datetime`](/integrations/input_datetime) to the desired time and then use that [`input_datetime`](/integrations/input_datetime) as an automation trigger to perform the desired actions at the set time.
+
+
+
## Sun trigger
### Sunset / Sunrise trigger
@@ -589,6 +605,14 @@ The `for` template(s) will be evaluated when the `value_template` becomes 'true'
Templates that do not contain an entity will be rendered once per minute.
+
+
+Use of the `for` option will not survive Home Assistant restart or the reload of automations. During restart or reload, automations that were awaiting `for` the trigger to pass, are reset.
+
+If for your use case this is undesired, you could consider using the automation to set an [`input_datetime`](/integrations/input_datetime) to the desired time and then use that [`input_datetime`](/integrations/input_datetime) as an automation trigger to perform the desired actions at the set time.
+
+
+
## Time trigger
The time trigger is configured to fire once a day at a specific time, or at a specific time on a specific date. There are three allowed formats: