Issue with Write to Other Table Triggering Premature Row Creation

I’m using the “Write to Other Table” enrichment and it’s returning that a row was successfully created before all the enrichments in the other table has run which is causing issues…does anyone know when the Write to Other Table triggers that a new row has been created? I don’t want this enrichment to return until all the other enrichments in the connected table have been run…

3 comments

Channeled
APP
·
·
The "write to table" feature typically runs when a new row is created or updated in the source table. However, there's no built-in mechanism to ensure it waits for all enrichments in the connected table to complete first. To control the order of execution, you can use a boolean formula to check if other enrichments have finished, then use that in a conditional formula for the "write to table" action. This allows you to set up a dependency between enrichments. If you're experiencing issues with the "write to table" function, you can try using the Force Run option in the table settings. For persistent problems, you might need to delete and recreate the affected column, then re-map your data. For more complex workflows or specific timing requirements, you may need to explore custom solutions or consult with our support team for advanced configurations.
Sources: Enrichments | Documentation | Clay University Enrichments | Documentation | Clay University
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.
Mike B.
·
·
Yeah I get it but if we are needing the records to run in that sub-function I don’t understand why it would return that a new row is created before it has completed the run…