Limits
An Automation is limited in the size of its graph, in a few node settings, and in the files it can select and process. The graph limits protect the platform that every site shares from one Automation that expands into too many nodes, and Files.com checks them when you save. The other limits belong to the node or the feature involved.
| Limit | Value | Explained on |
|---|---|---|
| Nodes in one Automation | 50 | |
| Automations nested through Run Automation | 5 deep | Run Automation |
| Nodes in the expanded graph, counting every selected Automation's nodes | 100 | Run Automation |
| Wait delay | 300 seconds | Wait |
| Send Email attachments, combined | 25 MB | Send Email |
| Transform node input and output | 100 MB per input file, 200 MB per output | Writing a TransformScript |
| Custom metadata keys per file | 32 | Custom Metadata |
| Files in a folder a Scheduled, Manual, or Webhook trigger selects from | 10,000 before performance degrades, 100,000 before the run fails | |
| Items in one run | No limit | |
| Duration of one run | No limit |
The folder limits apply when a trigger's folder path and pattern are evaluated to select files, because the folder's contents are listed to find the matches. They do not apply to a File Action trigger, because the file activity that starts the run identifies the files and the folder is not listed. To keep a folder under the limits, organize files into subfolders or set File Expiration on it.