Automations Pro FAQ

Q: Can Automations trigger Automations Pro?

No, Automations Pro and Automations cannot trigger each other. For example, adding data to a form, Form A, through Automations Pro will not trigger Automations to add records to the Form A. The reverse is also true.

Q: When modifying various data types within a form, should I add an Add Path node or multiple serial Update Record nodes?

The multiple serial Update Record nodes are recommended.

1. Why not the Add Path?

In this case, suppose an Add Path node is used, and there on each Path should be an Update Record node that is executed to update a data type, and the error notification, The form is executing other batch editing tasks , is likely to pop up.

The reason is that: When more than one Path Condition is met, the Update Record nodes on those Paths will be executed. Imagine an Update Record node A tries updating the data where a node B is currently being executed, their updating may conflict each other, causing the node A to fail.

2. How to add the multiple serial Update Record nodes?

Add them sequentially, and set filtering conditions for each node to select a specific data type.

An example of marking daily hot-selling products:

Due to the fact that the “hot-selling products” definition varies for different types of products (e.g., T-shirt sales > 100 is considered hot-selling, and jacket sales > 50 is considered hot), Automations Pro has to identify whether a type of product is hot-selling or not, to update the value on the Hot-Selling Status field. In this case, two Update Record nodes can be used:

Node 1: Add filtering conditions, Product Type equals T-shirt, and Daily Sales is greater than 100;
Node 2: Add filtering conditions, Product Type equals Jacket, and Daily Sales is greater than 50;

At this point, the nodes will be executed sequentially (without failure due to simultaneous execution), and each node will filter and update data only for its respective data type.

Q: Does Automations Pro have an automatic retry mechanism?

If the execution fails because The form is executing other batch editing tasks, Automations Pro will automatically retry 5 times, and the final execution result will be displayed in the execution log (during retries, the execution status of Automations Pro will be shown as retrying).

Q: Why can't Automations Pro be triggered?

The triggering logic of Automations Pro: after a trigger event occurs in the triggering form, Automations Pro undergoes condition validation before it can be triggered. Therefore, if Automations Pro fails to be triggered, check these two settings to identify the issue:

1. Check whether the trigger event is valid.

Trigger	Scenario	Reason and Solution
Update record	Not triggered when updating data to its original value	Reason: If the updated value remains the same as the original one, it is not considered a valid update event. Solution: To trigger Automations Pro through Update Record, there needs to be a change in field values.
Delete record	Not triggered when deleting subform records	Reason: Only deleting the entire data entry is considered as a deletion event. Solution: Rather than deletion, deleting subform records is seen as an update event. Thus, set the Trigger as Update Record to trigger Automations Pro.

2. Check whether the triggering conditions are met.

When there are multiple triggering conditions, the default logical relationship between them is and. If not all conditions are met, the trigger event will not occur. Therefore:

If the actual logical relationship between multiple conditions is and, check whether all conditions are met;
If the actual logical relationship between multiple conditions is or, you can switch the logical relationship to any of.

Q: After Automations Pro executes an update and the execution log shows that execution, why is there no corresponding record on the data log?

When the values of a record before and after update are the same, the execution will not be recorded in the data log. You can check whether the record has been updated by viewing the latest update time of the record.

Q: Can modifications implemented through Automations Pro trigger Webhook?

Yes, and the modifications include:

adding single/multiple records
deleting a single record
updating a single record

Q: How to correctly configure the Update Record node?

When you try adding the Update Record node, after selecting the target form/node, it's essential to set the following 3 sections correctly for Automations Pro to accurately locate the records to update, and determine what values to set.

For example, to configure a Update Record node that updates the quantity of jackets and shirts in an order with the Order Number as Jodoo-001, you should:

Steps	Instructions
Filter and select the records to update	Add a filtering condition to select the specific form records. In this case: Filter for orders with the Order Number as Jodoo-001.
Set the field values	Add the fields to be updated, and set their values. It is to tell Automations Pro what you want to update the target records to. In this case: You want to update the Quantity according to the updated order.
Add matching conditions for the target records to match with the source records	Set a many-to-many matching relationship: If there is only one record in the data source and only one record to be updated, they will naturally be matched, and the update succeeds. When there are multiple records in the data source and multiple records to be updated, Automations Pro does not know which record or records to update when it retrieves one record from the data source. Therefore, it is necessary to establish many-to-many matching relationships, such as "records to be updated: product name = data source: product name," so that "Automations Pro" knows to use the records with "shirt" as the product name to match and update the records with "shirt" as the product name, rather than other product records. Note: No update will be executed on unmatched target records.

Note:

1. If the configuration item for the Step 3 does not appear, no configuration is required.

2. For the details on the configuration steps and execution logic, see Guide on Using the Update Record Node.

Q: Does Automations Pro have a time limit for execution?

In Automations Pro, the Delete Record nodes do not have a time limit. However, the following nodes may fail due to execution timeout:

The Plugin node: 1 minute
The Query Record/Records node: 30 seconds
The Update Record node: 30 seconds, if it is set to update Record in the form.

Q: Why didn't Automations Pro trigger despite configuring a Update trigger and submitting the workflow?

If no update operations are executed at the workflow node and the workflow is directly submitted, it will not be considered as an update action and thus will not trigger Automations Pro.

Here are the solutions:

Solution 1: Modify the Trigger to Workflow flows to next node.
Solution 2: Add an auxiliary field to the workflow form and update this field when submitting the workflow to trigger Automations Pro.

Q: Is it possible to delete data from a subform?

No, it is not supported. Even if you use subfields in a Delete Record node’s Conditions, the objects for filtering and deletion remain the entire entry.

Q: Can the Update Record node be used without filtering conditions?

A: Yes, it can. Above the Update Record node, add a Query Record/Records node to retrieve the data that need to be updated. Then, set the target as Record at the node, and select the Query Record/Records node as the data source.

Q: What actions will not trigger Automations Pro:

1. Importing records;

2. Synchronizing the Output form records to other forms;

3. Batch Update (When Query Record/Records is selected, the action will not trigger Automations Pro);

4. Batch Deletion (If Query Records is selected before the deleting, Automations Pro will not be triggered when records/selected records/all the records are deleted. It will be triggered, however, if Query Record is selected.)

Q: In Automations Pro, there are the following quantity limits:

1. The Delete Record node: Up to 200 records can be deleted at a time.

2. The Query Records node: Up to 200 records can be queried at a time.

3. The Add Record node: Up to 200 records can be added at a time, and within each record, up to 200 subform record can be added.

If an Automations Pro can trigger other Automations Pro, they form a nested trigger system and several trigger series (in the diagram below, the Pro 1 to 6 form a nested structure; the Pro 1 >> Pro 2 >> Pro 4, the Pro 1 >> Pro 3 >> Pro 5, and the Pro 1 >> Pro 3 >> Pro 6 are three trigger series). In this case, there are additional quantity limits:

Within a single trigger series, a maximum of 1000 records can be added cumulatively.
Within the entire trigger system, a maximum of 10,000 records can be added cumulatively each hour.

4. The Update Record node: Up to 200 records can be modified at a time.

Additionally, this node supports updating multiple subform records from another form, but there is a quantity limit: when the calculation of matching records reaches SUM(Target Data.SubForm Data Quantity * Source Data Quantity * Number of Matching Conditions) is less than or equal to 1,000,000, the udpate can continue; otherwise, it will fail.

For example, in synchronizing changes to inventory data, after initiating a purchase update request, the warehouse for multiple products in the corresponding inbound record is updated together. If the warehouse for desks and A4 paper is updated, the calculation should be: SUM(3*2*1) = 6.

Note:

At the Update Record node, if the modification includes both Update Record and Add Record, the limit on the quantity of added records is the same as that of the Add Record node.

Q: How many records at most can be triggered at a single time by a Notification with the Timing set as Choose a Date&Time field?

At the same time, a maximum of 500 data entries can be triggered in a single instance.

Q: Can Automations Pro be triggered by automatic submission of workflows?

Automations Pro can be triggered by automatic submission in the following scenario:

In the workflow form when Workflow flows to the next node from the node A, Automations Pro is triggered. The workflow form should be set as follows:

Overdue Actions are set (auto-submit);
Under When No Approver is Found, select Stop flowing and report an error. When the workflow flows from the Workflow node to the No Approver is Found node, and the No Approver is Found node automatically submits the record, Automations Pro can be triggered:

Automations Pro can be triggered when the workflow is designed as … >> the Workflow node >> the No Approver is Found node;
Automations Pro cannot be triggered if the workflow is designed as … > the Plugin/Child Workflow node > the No Approver is Found node.

Q: Why can't I select the subfields?

In the filtering condition, switch the relationship from equals/not equals to equals any of/is not equal to any of, and you can select the subfields.