Clay Data Registration Issue with Workflow Status Formula

Hey team, here's the table, Clay isn't registering new data if its from a differnet source and pushed into existing fields: https://app.clay.com/workspaces/449716/workbooks/wb_0szi1qfRWJWdXAYozzM/tables/t_0szi1rfu7xQqHrqGgoZ/views/gv_0szi1rfaV69McBuasJi As it shows here, the column "Workflow Status" formula isn't output results for new data "write to table" from https://app.clay.com/workspaces/449716/workbooks/wb_0szi1qfRWJWdXAYozzM/tables/t_0szi5jh89itedSexPYp/views/gv_0szi5jhSyHc9eqvJmkS

13 comments

Clay
APP
·
·
When new data from "write to table" isn't triggering formulas in existing columns, Clay doesn't automatically reprocess previously generated data. Try these solutions: 1. Force Run: Use the Force Run option in table settings to reprocess the affected column. 2. Refresh the formula column: Delete the "Workflow Status" column and create a fresh one, then re-map your data. 3. Re-run the step: Delete and re-run the step that generated the original data to see updated results. The formula should then process the new data from your write to table integration.
Sources: Sources | Documentation | Clay University Sources | Documentation | Clay University Write to Other Table | Documentation | Clay University
Andi D.
·
·
can't "force run" a formula
Andi D.
·
·
Highlighted the column in red for you guys to see it. Check out rows 1-200
LuisArturo
·
·
Hey there Andi thanks for reaching out sorry for the delay here, just want to clarify that the issue that you're seeing here between both of these tables, is that the data that's being sent from the first table is being completely ignored in the second one and this is causing your formula column to not generate the actual results? Just want to make sure we have the right grasp on what the issue is so that we can better diagnose it and let the team know about it
Andi D.
·
·
Thanks Luis! The data moves from Table 1 --> Table 2 perfectly fine. But once it's in Table 2, the Formula Column isn't "seeing" the new data
LuisArturo
·
·
Yes I'm seeing this occur here, the issue here, is that when using a Write to Table, there is no "source" column that gets created for the newly added data here. Made a loom going into more detail: https://www.loom.com/share/4ad6b3859ccf4d93881a3c5af6d0db6d?sid=9deaa453-17ee-4f61-9edc-b2694ac187c6 One thing I would recommend though is the next time you try this workflow is to use, Send Table Data, as this will create a source column for you to use.
Andi D.
·
·
Ah so if there’s no source it wouldn’t see the data… interesting But the issues with Send Table Data it overwrites other sources
LuisArturo
·
·
How so, do you mean as is the Apify column will get written over here?
Andi D.
·
·
hum, not sure actually, but last time I used Send Table Data to an existing table, it wiped out existing data in it. Support confirmed that when/if using Send Table Data it would overwrites the columns
LuisArturo
·
·
Hm thank you for clarifying let me take a look into this for you.
🙏1
Andi D.
·
·
LuisArturo nvm you can drop it!
Andi D.
·
·
it was a dumb mistake, the Formula was pulling info from the source column not the extrapolated column
LuisArturo
·
·
no worries here, happy to help

Clay Data Registration Issue with Workflow Status Formula | Clay