Scale and property limits

Several limits are in place to prevent Actions from affecting data freshness, including:

• Edit limits
• Supported property types
• Additional limits
  • Inline edits
  • Notification recipients

Edit limits

The edit limit for each Action submission is 10,000 object edits.

• Modifying a number of properties on a single object resolves to just one edit, so reaching 10,000 edits is possible if an Action is editing a large number of objects, but less likely in cases that involve many edits to a smaller number of objects.
• Note that object reference parameters with a maximum selection size of > 1000 are not permitted as part of submission criteria. Attempting to save such parameters not permitted in submission criteria will result in an error.

These limits ensure the object-backing databases can quickly process edits and update user-facing data without slowing down live applications. Actions submitted that exceed these limits will not succeed and will display an error message to the user.

Supported property types

Actions does not currently support editing float, byte, short, decimal, or geo time-series property types.

Supported properties

Currently, Actions cannot be used to edit the primary key of an object. Modifying the primary key is equivalent to deleting an object and then adding a new object; instead of editing the primary key with an Action, you can create or delete an object directly using rules.

Additional limits

Notification recipients

When using side effect notifications, a maximum of 500 recipients can notified in a single Action. This limit is reduced to fifty recipients when notifications content is rendered "From a Function". For further information about limits to account for when generating notifications, see the documentation on maximum recipient limits for notifications.