Limits

Preview limits for Triggers.

Triggers

One event type can associate with a maximum of 32 triggers.
Only execution of Cloud Code scripts and modules is supported.
Processing of events in order is not guaranteed.
Triggers support at-least-once delivery semantics. This means that all events are guaranteed to be processed once, but may occasionally be processed multiple times due to network issues.
Triggers do not interact with the return value of the Cloud Code script or module. You should account for this and execute your game logic in the script or module itself.
Cloud Code scripts or modules that rely on external calls using client-side authentication don't work due to the lack of a player context. Refer to Set up Cloud Code: Context attributes for more information.
Cloud Code script and module execution timeouts still apply.
If your trigger interacts with the same service that emits the event, you should define a filter to avoid infinite loops. Infinite loops overprocess the event, cause unexpected behavior in your game, and eventually exhaust your Cloud Code resources for the project, which can lead to a service outage. If you encounter this issue, delete the trigger that causes the loop.

Recurring schedules only support cron expressions.
Recurring schedules have a minimum scheduled frequency of once per hour.
The maximum payload size is limited to 1kb.
The maximum amount of active schedule configurations is 900.
The scheduling feature is included in Cloud Code price and currently limited to 25,000 invocations coming from set schedules per month. This would cover the implementation of 30 hourly schedules.

Only Service Account authentication is supported.
The Triggers API service limits each Service Account to 600 requests per minute.
The Scheduler API service limits each Service Account to 600 requests per minute.
The Scheduler API List endpoint limits each Service Account to 120 requests per minute.