[DONE] Calculation field change not triggering automation

🔧 Bugs & Issues
,
1

I had this in the past ([DONE] Calculation fields are allowed to trigger automations, but don't do it?) but its still unreliable and seems to be broken.

  • I have a record, that holds a given number (expected value).
  • I have a calculation, that counts linked records (current value).
  • Once the difference is 0, the watched calculation field switches to “done”.

Now an automation should start, but it still doesn’t.

It was also discussed here: Trigger automation by update in calculation field

Could you please look into it again?

2 Likes
2

I almost wanted to applaud when it worked once today. But the next time it missed the calculation field change again and didn’t trigger the automation.

1 Like
3

Hi @dirk_s,

Many thanks for the report :100:

We already started looking into this and will keep you updated as soon as we have a first insight, or even better, a fix. Since the issue seems to happen only occasionally, we’ll first set up a test scenario to reproduce it reliably.

Once we can reproduce it, we’ll make sure to close the gap so that automations always trigger correctly when calculation fields change!

Thanks again for pointing this out, and have a great weekend!

Best,
Leo

4

Hi @dirk_s,

we appreciate the report and your persistence.

We checked on our end via a reproduction scenario, and indeed found a timing bug that could lead to calculation field updates not triggering workflows in some cases. That fix was deployed over the weekend and is now live. :train2:

An additional important note: In order for this to work, the origin update (that triggers the calculation update) needs to have the “Trigger automations” switcher on, which propagates transitively through an update → caluclation cascade.

In your case, is the origin update performed manually, via the API or also via automations? :information_source:

Looking forward to your feedback so we can resolve this together.

Cheers
Tim

1 Like
5

Hi @Tim - great! I will test it right away.

The scenario is as follows:

  • an automation starts a regular poll of a number of issues,
  • in order not to work with delays, the calculation field compares the expected number of issues with the number of linked records - I will make sure, that the automation that links the record will have the control switched on for triggering automations
  • once the number of linked records matches the number of expected issues, the calculation field switches to done and should trigger the next automation

Will let you know if that works now reliably.

1 Like
6

After roughly 48h I can confirm the job now runs as expected!
Great that this is now finally fixed :wink:

2 Likes