Changing a calculation field may trigger massive automation action - best practice?

[dirk_s]

Hi there,
sometimes when I refine an app, I improve calculation fields. Its not very obvious, if they of any field depending on that field, will trigger a massive automation batch.

How do you handle this? Should there be a warning?

[DigiTom]

We experienced the same issue in the past when building apps. Many automations were triggered, and we would have appreciated a notification as well.

However, I would probably dismiss the notification every time anyway. That’s why we built everything based on recommendations, ensuring that only specific fields trigger the automation: (What I didn’t realize for a long time is that multiple fields can be selected at the same time)

[UPGRADE ️] The "Record Updated" trigger now includes dedicated configuration for more precise control

With this new update, you can reduce background noise in your organization and optimize automation performance. The trigger ‘When a record is updated’ can create a certain performance overhead, starting every time a record is updated — even if the filter conditions weren’t met. Here’s a simple example for non-technical users: Imagine an app with 20 fields. Automation: If a record is updated and the Status field changes to “Done,” then change the date field. Even if you updated on…

For the calculation field I’m currently working on, I’ll simply exclude it. This approach works really well for us now.