There are various limits enforced by Catalytic, but we believe your work shouldn’t stop because of these limits. The most you’ll likely notice is the occasional task or instance that takes a bit longer to complete because the scale of the automation.
When you reach a limit, our system manages the issue on its own or provides immediate feedback. For example, if an uploaded file is too large we provide immediate feedback. If too many tasks start at once, the work will be smartly queued and completed as soon as possible without interrupting your work.
Limits ensure a high-quality experience for you and your team and help limit interruptions to processes and actions.
What are the current system limits?
Max instances running at a time
Total number of fields per instance
Total number of tasks per instance
Field size (non-file)
Total field size per instance
Instance starts per team
Instance starts per process
Any instances over this amount are queued.
⚠️ Heads-up: The Field size is the maximum data available per field, but not the maximum file size. For example, 128kB is around 122,000 characters, or 20,500 words, or 82 solid pages of text. A fix task is created if a Workflow tries to save more than 128kB to a field.
Master and Application Data tables
64kB of data
If a master or application data table exceeds 100,000 rows, the oldest instances over 100,000 will not be visible. If you export the table, only the last 100,000 rows are exported.
Imported Data Tables
128kB of data
Total cell size within a table
1GB total cell size
**Column, row, and cell limits
Catalytic employs soft and hard limits to ensure a high-quality experience for you and your team and help limit interruptions to processes and actions.
Performance can degrade significantly after the soft limit. If the hard limit is reached, a fix task is created.