deploy: 4af33015af

develop/modules/third_party_rules_callbacks.html

@@ -263,6 +263,9 @@ any of the subsequent implementations of this callback.</p>
 <p>Called after sending an event into a room. The module is passed the event, as well
 as the state of the room <em>after</em> the event. This means that if the event is a state event,
 it will be included in this state.</p>
+<p>The state map may not be complete if Synapse hasn't yet loaded the full state
+of the room. This can happen for events in rooms that were just joined from
+a remote server.</p>
 <p>Note that this callback is called when the event has already been processed and stored
 into the room, which means this callback cannot be used to deny persisting the event. To
 deny an incoming event, see <a href="spam_checker_callbacks.html#check_event_for_spam"><code>check_event_for_spam</code></a> instead.</p>

develop/print.html

@@ -10593,6 +10593,9 @@ any of the subsequent implementations of this callback.</p>
 <p>Called after sending an event into a room. The module is passed the event, as well
 as the state of the room <em>after</em> the event. This means that if the event is a state event,
 it will be included in this state.</p>
+<p>The state map may not be complete if Synapse hasn't yet loaded the full state
+of the room. This can happen for events in rooms that were just joined from
+a remote server.</p>
 <p>Note that this callback is called when the event has already been processed and stored
 into the room, which means this callback cannot be used to deny persisting the event. To
 deny an incoming event, see <a href="modules/spam_checker_callbacks.html#check_event_for_spam"><code>check_event_for_spam</code></a> instead.</p>