Skip to main content
Solved

"An error occurred when evaluating conditional group" - Automation

D
Forum|alt.badge.img+8

Hello there

i have an automation that was working fine, now when i try to test it, i can't get past the trigger. the trigger works, but when i try to evaluate the conditions for the first action group (or any other action group) i get an error instead of an "yes, matches conditions" or "no, doesn't match conditions". strangely, this automation worked until now. is the error possible related to airtable general maintenance or issues and not to my automation at all. or do you guys know what kind of conditions throw such an error instead of getting evaluated. very strange 😞

Best answer by jadeadele

jadeadele wrote:

this is happening to all of my automations. Any insight?


If anyone runs into this: for me it's because I accidentally went over my automation run limit while building my database and running way too many tests. Word of caution, be more conservative about your tests!! 

View original
Did this topic help you find an answer to your question?

7 replies

Z
Forum|alt.badge.img+2
  • Zwerik
  • New Participant
  • 2 replies
  • March 14, 2023

I'm experiencing the same issue here @Davidt. Have you been able to resolve this?

A
1 person likes this
  • A
    Aldo_Silva
J
Forum|alt.badge.img+4
  • jadeadele
  • Inspiring
  • 9 replies
  • March 21, 2023
Zwerik wrote:

I'm experiencing the same issue here @Davidt. Have you been able to resolve this?


this is happening to all of my automations. Any insight?

J
Forum|alt.badge.img+4
  • jadeadele
  • Inspiring
  • 9 replies
  • Answer
  • March 21, 2023
jadeadele wrote:

this is happening to all of my automations. Any insight?


If anyone runs into this: for me it's because I accidentally went over my automation run limit while building my database and running way too many tests. Word of caution, be more conservative about your tests!! 

C
1 person likes this
  • C
    Christian_Roy
C
Forum|alt.badge.img+4
  • Christian_Roy
  • Participating Frequently
  • 6 replies
  • March 31, 2023
jadeadele wrote:

If anyone runs into this: for me it's because I accidentally went over my automation run limit while building my database and running way too many tests. Word of caution, be more conservative about your tests!! 


Thanks! This was also the problem in my case. The error message is very misleading (I spent a lot of time trying to figure out what was wrong with my conditional group!).

Calvin_Young2
Forum|alt.badge.img+12
  • Calvin_Young2
  • Known Participant
  • 25 replies
  • November 21, 2023

This extremely unhelpful code was cropping up in one of my automations, despite not being over the limits... and it took me a while but I found the solution.

One of my conditions was checking if {Completion} < 1 where {Completion} is a formula field formatted that properly recognizes numerical formatting.  I saw grumblings in another forum post which alluded to the fact that formulas referencing lookup fields can sneakily pass through an array rather than a number which can cause automations to fail.

I thought that the new feature in the lookup field configuration to "Limit the number of items shown to the first 1" would force the lookup to return a single value, but it still appeared to be passing an array with a single number.  So I altered my formula field to explicitly cast the lookup field to a string and then a number. The resulting formula:

{Completion (Lookup)} & "" + 0

M
1 person likes this
  • M
    Meredith_Scrog1
M
Forum|alt.badge.img+10
Calvin_Young2 wrote:

This extremely unhelpful code was cropping up in one of my automations, despite not being over the limits... and it took me a while but I found the solution.

One of my conditions was checking if {Completion} < 1 where {Completion} is a formula field formatted that properly recognizes numerical formatting.  I saw grumblings in another forum post which alluded to the fact that formulas referencing lookup fields can sneakily pass through an array rather than a number which can cause automations to fail.

I thought that the new feature in the lookup field configuration to "Limit the number of items shown to the first 1" would force the lookup to return a single value, but it still appeared to be passing an array with a single number.  So I altered my formula field to explicitly cast the lookup field to a string and then a number. The resulting formula:

{Completion (Lookup)} & "" + 0


This comment just saved me so headache and frustration - THANK YOU!!!!!

D
Forum|alt.badge.img+8
  • Davidt
  • Author
  • Inspiring
  • 9 replies
  • July 8, 2024

Seems like this can be caused by various issues. Check your formulas and fields. Potentially it's related to:

  • Lookup fields providing arrays instead of strings/values.
  • Changes in field definitions or conditions in lookup fields (check your fields and look out for the red exclamation mark)
  • Maybe running over automation limits...check your account for quota.

Reply


Most helpful members this week

Terms & Conditions