![]() ![]() Two or more automations within the same base are conflicting with one another in a way that causes one automation to trigger another and so on.Reach out to our support team if this occurred on accident so that we can help to reset your run counter for the month. If the conditions in the automation cause the newly created record to enter the view from the trigger step, then, once turned on, this automation will loop endlessly until you've exhausted your workspaces plan limits. One example would be using the "When a record enters a view" trigger alongside the "Create a new record" action. The action step of your automation is retriggering the trigger step of your automation.Alternatively, you can reduce the total number of records in the base until it is once again under its workspace plan’s record threshold. To fix this issue, upgrade the workspace for the base in question to increase its record and storage limits. New records can no longer be added because the base that the automation is attempting to create a record in is currently over its plan’s record limits.We do not currently support using mathematical operations to set field values within Automation actions. If you see an error containing the phrase, "Could not parse number", the action is probably failing because you are attempting to set a field's value using a mathematical operation.You can add the email address into that particular record's email field and rerun the automation. To fix this, look at the run history for information on which failed runs were associated with records missing an email address. An example of this might be the " Send an email " action where a valid email address is needed for the email to send out. A record that triggered the automation to run is missing a necessary value for the action step to run.To fix this, go to the trigger step and retest that step so that you see the "Test ran successfully" message. The trigger step in the automation has not been successfully tested yet.Those processes are discussed in the linked articles above.Įrrors in action steps can happen for many reasons. For Google Workspace, Outlook, or other externally-based triggers, make sure that you have successfully connected (authorized) the external account with Airtable. The trigger links to an external service that is not currently connected to your Airtable account.For example, if the trigger has been set up to watch for any records containing a "Finished" status, then make sure that the record's status field is set to "Finished." This new record needs to contain information that will match any conditions set forth by the trigger step that was set up. For example, there needs to be at least one row in the Google Sheet that you are connecting to Airtable in order to properly test the " New row trigger for Google Sheets." To solve this, add a new "test record" (or matching external condition) to the particular table and/or view that the automation is watching. The same holds true for external triggers. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |