Mark L.

Hey there. Looks like that worked out for me, when testing as follows:

What do you see, when you try the same approach? In my test Lemlist, I see the default Owner field populated on the contact.

Sure, as a very very simplified example, we might have intent like "Only run this step if we have both a Company and a Website (so we can enrich the company reliably)."

A bad version of this formula would be:

{{Company}} && {{Website}}

- If both are present, this would return the Website value (a string), not true.

- If either is missing, it returns "" or null, not false.

Better would be:

!!({{Company}} && {{Website}})

That way if either is null or an "" empty string, we get back false.

It's possible that the 'Is Valid Company' formula had such a logic/definition change. Or, it's possible that one of the other formulas it depended on had such a change, and where previously it was providing null or empty values, it's not providing feeding "better" values that can be evaluated cleanly. This is a bit abstract, but I hope it illustrates the general idea.

Hey Luke, I don't think there were any application changes in how Clay evaluates formulas. It's possible the definition/logic of the formula itself has changed. (E.g. sometimes a formula definition won't strictly evaluate to a clean/true false, depending on the logic and its inputs.)

In the current state, I'm interested to know if 1) any new rows still have the issue you're referring to, and 2) any older rows, when re-run, still have the same issue.

Thanks for following up on this! Glad to hear all is well.

Hey there, we've just pushed an update for that issue in AI columns, where it was showing a validation error... even though cells could process okay. Things look good on our end – let me know if you don't see the same on yours!

I have this ticket linked to that internal work, so we can follow up when it's ironed out for good.

There is – thanks for flagging that. We've seen the tester/validation tool return false positives. As long as the cells are working, all is well, but it is a visual nuisance.

Hey Rees, thanks for getting in touch. This table, right?

https://app.clay.com/workspaces/129264/workbooks/wb_0t5bfvjPcBShad6mv3w/tables/t_0t5bga0AXEz8ppRwTDi/views/gv_0t5mpyctQXVtgeDhJUC

I didn't see any cells with the error that was displaying in your screenshot. Are you still seeing that?

We've resolved this incident affecting AI columns. Thanks again for reporting this, and please let us know if you see issues like this again!

We've resolved this incident affecting AI columns. Thanks again for reporting this, and please let us know if you see issues like this again!