Automation Pro Does Not Trigger
Problem Description
After designing and enabling Automation Pro, it fails to trigger at the scheduled time or upon data manipulation. No action is executed, and no corresponding logs are generated in the execution log.
Troubleshooting Steps
Step 1: Check for System-Level Trigger Restrictions
Review the following system limitations that may prevent Automation Pro from triggering:
Restriction Type | Description |
Bulk Operations | The following scenarios don't support triggering Automation Pro:
|
Workflow Triggers | If the trigger is set to when you "update a record," simply submitting a workflow without changing any data is not considered a modification. Change the trigger to when "workflow flows to next node" to resolve this. |
Scheduled Triggers | If a trigger is scheduled based on "Date&Time field" in the form, and more than 500 records meet the trigger conditions at the exact same time, Automation Pro will not trigger. |
Cascading Triggers | Automation Pro and the legacy automation cannot trigger each other. |
Looping Triggers | Looping configurations are supported, but the automation will only execute once and then stop to prevent infinite loops. |
Step 2: Verify Trigger Node Configuration
Ensure the trigger node is configured correctly for your specific scenario:
Trigger Configuration | Check Item | Explanation |
Form Trigger | Confirm that the correct trigger action is added. | --- |
Form Trigger | If the trigger is "Update Record - specific fields," ensure the correct fields are selected. | Modifying other fields will not trigger the automation. |
Workflow Trigger | Verify that the selected node and node action match the actual workflow execution. | If the executed node or action does not match the configuration, it will not trigger. |
Scheduled Trigger | Check the end time configuration in the trigger node. | If the scheduled trigger time is after the configured end time, the trigger will not be activated. |
Scheduled Trigger | Ensure the time and repetition rules are correctly configured. | --- |
Trigger Conditions | Confirm whether the conditions should be met on an "all of" or "any" basis. | --- |
Automation Pro Triggers Multiple Times
Problem Description
A single data operation by a user causes Automation Pro to trigger and execute multiple times. The execution log shows multiple records in a short period.
Troubleshooting Steps
Step 1: Check the Trigger User
Review the execution logs to see if the triggers were initiated by the same user. Multiple triggers may be caused by different users performing actions simultaneously.
Step 2: Check the Trigger Actions
If the trigger actions in the logs are different, it is likely that multiple trigger actions were selected in the configuration. Adjust the trigger node to retain only the necessary trigger action.
Execution Result Shows "Failed"
Problem Description
Automation Pro runs but does not produce the expected result. The execution log shows a "Failed" status.
Troubleshooting Steps
Click "View Details" to go to the node execution details page and identify the failed node.
Select the failed node to view the failure reason and suggested solution in the "Trigger History". Common failure reasons and solutions are listed below:
Failure Reason | Description | Solution |
Operation failed because another bulk edit task is in progress. | The form was locked by another bulk edit operation, such as a data import, API batch update, or another automation. | Wait a moment and then manually retry the operation. |
Failed to acquire lock. | The form was locked by another simultaneous operation, such as a data update, aggregation calculation, or another automation. | Wait a moment and then manually retry, or adjust the configuration of the automations to avoid conflicts. |
Modification Succeeded, but No Data Log Entry
Problem Description
The execution log shows that the modification operation was successful, but there is no corresponding entry in the data log for that record.
Troubleshooting Steps
Check if the value of the field being modified is identical to the new value. If they are the same, the modification is considered redundant and is not recorded in the data log. This is normal behavior. You can confirm the update by checking the execution log or the record's "Last Updated" timestamp.