Luke G.

Hi Mark L. Sayli G., Happy New Year ! We have reviewed the formula field and the formula fields that are rolling up to that formula as well but are still unable to identify the issue here. Is there any way somebody can jump on a call with us to review? cc: Guy H.

Hi Mark L. can you give me an example of what you mean? What could make the formula definition not evaluate to a clean true/false? The most recent import we ran was on the 10th and yes, the issue was present. It was sporadic, though, everybody's favorite kind of bug to troubleshoot 😬 When older rows are re-run the issue is no longer there.

Hi Sayli G. I'm still not 100% clear on what the issue was and if Clay deployed a technical solution for it? I wouldn't want to create a new formula and update all of the dependencies just for this to continue happening after that work is done.

Hi Bo (. thanks for the explanation, but I am still struggling to understand what you mean by 'stored in an older format'. Did Clay have an issue with this field and perform a deployment recently? I understand that lookup is not a live sync, however, there are rows here in the people table which I already re-ran (created on December 10th via import to the company table) which have this problem. So if there was a change to the format of the formula field made by Clay, when exactly was that done? Running the lookups on a schedule won't be a great solution for us because downstream enrichments would also be running on a schedule, wasting credits and providing data that we already paid for.

Hi Daniela, can you please clarify what you mean by 'previous version of the true/false field'? I understand that re-running resolves the problem but this issue was raised previously, the solution to re-run the cell was suggested, but it occurred again. Meaning - this is a bug and not just a one-off issue. It's not scalable for us to have to re-run the cells every time that new companies are pulled into the population. We need to be able to be confident that the setup is producing the expected results the first time. We can't be expected to continuously troubleshoot errors.

Hi Daniela D. thank you, appreciate the help and looking forward to the response.

yes, that is the case. In the table s I've provided, though I've only been able to identify examples where it returns an error aka. neither true/false in the response

The table URLS are posted in my previous message describing the issue

Hi, this was not helpful, I would like an engineer to look at why the data is only syncing sporadically.

OK, the initial Company search has a formula field called "Is Valid Company" which evaluates based on a set of criteria. This table then runs an Update People Table type column called '200+' that uses "Is Valid Company" = True in the 'Only run if' condition. ie: the People Search could never be updated in the first place unless this formula evaluates Once we move into the People table , we run a get request back to the Company table using a 'Company Lookup' column. This column should be able to return 'Is Valid Company' in the JSON since the formula is already evaluated. Sporadically, we are seeing an error (and in other workbooks a false value instead of true) which has downstream effects in the number of leads the workbook is able to identify for our sellers. Notice that some rows have actually evaluated and others have the error message. This is absolutely a bug and should be evaluated as such. tagging Guy H. who I believe has reached out about this previously.