Clarify the workers that the ThirdPartyRules' `on_new_event` callback will run on (#15071)
parent
647ff3ef65
commit
91f8de7b56
|
@ -0,0 +1 @@
|
||||||
|
Clarify which worker processes the ThirdPartyRules' [`on_new_event`](https://matrix-org.github.io/synapse/v1.78/modules/third_party_rules_callbacks.html#on_new_event) module API callback runs on.
|
|
@ -146,6 +146,9 @@ Note that this callback is called when the event has already been processed and
|
||||||
into the room, which means this callback cannot be used to deny persisting the event. To
|
into the room, which means this callback cannot be used to deny persisting the event. To
|
||||||
deny an incoming event, see [`check_event_for_spam`](spam_checker_callbacks.md#check_event_for_spam) instead.
|
deny an incoming event, see [`check_event_for_spam`](spam_checker_callbacks.md#check_event_for_spam) instead.
|
||||||
|
|
||||||
|
For any given event, this callback will be called on every worker process, even if that worker will not end up
|
||||||
|
acting on that event. This callback will not be called for events that are marked as rejected.
|
||||||
|
|
||||||
If multiple modules implement this callback, Synapse runs them all in order.
|
If multiple modules implement this callback, Synapse runs them all in order.
|
||||||
|
|
||||||
### `check_can_shutdown_room`
|
### `check_can_shutdown_room`
|
||||||
|
|
Loading…
Reference in New Issue