Seatable
Day 31 after signup
7 Reasons Your Automations Aren't Running as Expected
It's usually just one small setting. Use the quick checklist to find it in minutes.
Why it works
- Organize troubleshooting advice as specific, numbered causes so readers can scan for the issue that matches their situation.
- Follow the detailed explanations with a concise checklist, then provide clear next steps for readers who still need help.
How it is built
- Navigation links
- Troubleshooting headline
- Seven common causes
- Quick checklist
Email copy
Templates Help Blog Automations Automation Not Working? Start Here Dear SeaTable Community, When an automation in SeaTable doesn't run as planned, you can usually narrow down the cause quickly if you know where to look. Here are the seven most common causes we see: 1. Wrong trigger: Triggers behave differently, and switching the trigger often solves the problem. A classic example: the automation fires on every row change when you wanted it to run at a fixed time. Another: "Row is added" is selected when you need "Row is modified." 2. Wrong view: Triggers are tied to a specific table and view. If the trigger is set to your table's default view but you edit a record in a different view, the automation won't fire. 3. Wrong columns monitored: In addition to the table and view, you can choose which columns the trigger monitors. If you select specific columns, the automation only runs when a value in one of those columns changes. Changes in any other column won't trigger it. 4. One automation can't trigger another: If an automation adds a new row, that row won't start a second automation, even if its conditions are met. For cascading actions, use a Python script. You find more information about scripts in SeaTable in our new video. 5. Two automations interfere with each other: Two rules acting on the same column can overlap and produce incorrect results. In that case, try changing the trigger and running the second rule on a schedule instead of after every row change. 6. The automation isn't active: Check whether the automation is turned on or has been paused. 7. The action points to nothing: If the action refers to a column that was deleted or whose column type was changed, the automation will fire but won't complete the action correctly. Quick checklist 1. Is the right trigger selected? 2. Are the right table and view selected? 3. Are any additional conditions set? 4. Are you relying on a chain of automations? 5. Do multiple rules overlap? 6. Is the automation paused? 7. Does the action reference a column that no longer exists? Still stuck after going through the list? Check the automation's execution log, or describe your case in the SeaTable Forum. We're happy to help. Best regards! Patricia Steinberger Marketing How do you like SeaTable? Give us an honest feedback and review SeaTable on OMR Reviews! SeaTable GmbH, 117er Ehrenhof 5, 55118 Mainz, Germany Unsubscribe • Imprint • Security • Data privacy