Rate Limits

automations can enforce their own rate limit rules via a rate limiter system action automation rate limiters can be enforced at varying scope levels, including across multiple accounts individual actions can have a per account rate limit throttle defined as described here action assemblies docid\ btsf6wpnkx3zcefaloft9 automation rate limiters are stored in the server(s) memory before they can be invoked, they must first be created via the system app's "rate limiter create or update" action the typical approach (except when a single automation's scope is used) is to build two automations, one with a system app's "system booted (instant)" trigger and another with the system app's "no op" trigger since a developer typically cannot reboot the server at will to trigger the system booted trigger, the no op trigger automation can be run manually as needed to create and update the rate limiter rate limiters are specified by name and a scope the scope allows the rate limiter to be accessible among the following the current automation all automations in the account all automations in all linked accounts all automations in the entire tenant system note that when "this automation" is used as the scope, then there is no need to have separate automations to create/update the rate limiter the typical approach is to place the "rate limiter create or update" action as the first action in the automation with the rate limiter defined, it can then be used in one or more automations (depending on the configured scope), typically before actions that make api calls the "rate limiter invoke" action is configured with a scope and name that selects the rate limiter previously created with the "rate limiter create or update" action the "rate limiter invoke" action pauses as needed in order to not exceed the defined rate limit throttle a runtime error occurs if the rate limiter does not exist