Your merge column might be inconsistent because of how the "waterfall" priority works—Clay checks each column in order and only uses the first one with data. If some rows have data in earlier columns and others don’t, the merge will only fill in where it finds values. Also, if some source columns have stale or incomplete data, or if workflows haven’t finished processing, the merge may leave some rows empty.
To fix this:
Make sure all source columns are up to date and refreshed.
Check that auto-update is enabled so downstream columns update with new data.
Review your fallback formula to ensure it handles edge cases (like empty or invalid data).
Confirm all required workflows and checks have completed before reviewing results.
If you still need help resolving the inconsistency in your merge column, I’m here to assist. Would you like to provide more details about the specific rows or data sources involved?
