Hi, I found that automation triggers and formula fields are not “synchronized” to have a consistent state, in other words here is the sequence: I create an automation rule that is triggered by an entity create event. I create a new entity that has formula fields. The automation trigger is fired im…

[image] Giuse: The automation trigger is fired immediately after creation but before formula fields are calculated, so those fields, when accessed by a script action, are still null. That implies two issues: -) if the automation trigger filter is on a formula field => the automation is not run…

It can be a good idea, but are they filled “transactionally” so that I can use any formula field as the trigger? If the fields are updated “randomly” I can’t pick one (or more of them) as event trigger.

You can choose all of them in the update section of the trigger, and then add a set of filters which checks that they are all filled. Then it doesn’t matter the order in which they are calculated, the filter criteria will be met only when the last update has occurred.

I made some tests and unfortunately that workaround solves the problems of having formula fields filled but causes multiple triggered actions. Here is the sequence that happens: Define an automation rule with trigger on update on 2 formula fields and some non-formula fields, filter is the 2 field…

I’m not sure I get all the details of your use case, but it might be easiest to solve by just adding a formula field that returns true when all the fields that need to be populated are not empty. Then you can trigger on this field being updated to true.

Thanks, good idea, that works to replace the entity create event in presence of formula fields, but for entity update event… that this additional “is everything updated?” field would have a tough time to understand when the formula fields have their “final” values (it should replicate all formulas t…

As I said, I’m not sure I get all your details. Perhaps you want to explain the fields involved and the sequence of events that happen (making no assumptions about when formulas might get calculated) and highlight when you want things to happen (and when you don’t want things to happen), e.g. Task…

ok, that case works being a creation trigger with a simple formula, instead for example -) you have a formula field that takes a value only on a special condition of the entity, so it may be filled in or it may be empty if the special conditions are not met. In these cases you cannot just check if …

Can you give a concrete example, with the fields you have and what you want the automation to do. It’s possible you can solve it with formulas in the automation actions (not necessarily scripting).

Automation triggers and data inconsistency on formula fields

API & Programming

interr0bangr February 14, 2024, 2:13pm 2

A delay (or as you call it, sleep) action would be very helpful.

Topic		Replies	Views
Are formulas sometimes too slow for automations? Get Help	2	37	April 30, 2026
To be able to use Formula in Automation filters Automations	7	664	August 19, 2025
Trigger automation on specific date Automations	4	358	July 18, 2022
Possible to add more triggers to the rule Automations automations	5	362	February 7, 2022
👂 Feedback needed: scripts in automations that shouldn't be scripts News & Announcements	77	1681	May 22, 2026

Automation triggers and data inconsistency on formula fields

Related topics