Currently, the automations feature has the following limits:
You must have admin-level permissions to the app to view and build automations.
The last person to save an automation is considered the owner of the automation. The automation will fail if the automation owner doesn’t have permissions to make the changes defined in the automation’s actions. Keep this in mind when editing an automation that you didn’t create.
You must be the owner of an automation to delete the automation.
An app can have no more than 100 automations. This limit includes both enabled and disabled automations.
An automation can have no more than 50 actions.
An automation can’t run more than 10 times per second.
An automation times out after 30 seconds.
Modify records and Delete records will only work on 1,000 records or less. If an automation attempts to modify or delete more than 1,000 records in one action, it will error out.
Some field types are not fully supported in an automation:
When retrieving data from one field to another in an automation, make sure the data and field types are compatible. Data transformation is currently unsupported.
When you copy an app, the original app’s automations are not included with the copy.
Test as Role and Test as User won’t work for viewing and building automations.
Existing automations won't run if the realm's Host Name (realm URL) changes.
Automations will not work if your organization uses IP whitelisting.
© 1999-2018 QuickBase, Inc. All rights reserved. Legal Notices.