Several limits are in place to ensure edited object types 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.
The Allow multiple values toggle allows users to pass in a list of values to a parameter.
| Limit | Maximum |
|---|---|
| Number of elements in a primitive list parameter | 10,000 |
| Number of elements in an object reference list parameter | 1,000 |
| Number of elements in a list parameter when used in submission criteria | 1,000 |
| Limit | Maximum |
|---|---|
| Number of Object Types you can edit in a single Action submission | 50 |
| Number of objects you can edit in a single Action submission | 10,000 |
| Each individual edit of an object in an Action submission | 32KB (OSv1), 3MB (OSv2) |
An Action can be called a maximum of 10,000 times in a batch. This limit is reduced to 20 when the Action is Function-backed and the Function is not configured to use batched execution.
The edits applied in a batched Action call are treated as a single group when enforcing edit limits, regardless of which request in the batch was the cause of the edits.
Additional limits may apply, depending on the calling application.
Actions does not currently support editing float, byte, short, decimal, or geo time-series property types.
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.
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.