Clay Icon

Troubleshooting Contact Enrichment Formula and Data Staleness Issues

·
·

Hey Team 🙂 I've setup a formula to determine if a contact should be enriched (by returning "safe to send"). When I try and run the table, the LI profile enrichment column (which is dependent on the "safe to send" column to run) is very patch and misses some rows. It then says it cant run because the data is stale. Would you mind taking a look to see what's going wrong? https://app.clay.com/workspaces/223473/tables/t_kDsAp2gtWUpP/views/gv_KbCVMXZRpcKk

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

    👋 Hey there! Our support team has got your message - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in this thread so that we can help you as quickly as possible!

  • Avatar of Bo (.
    Bo (.
    ·
    ·

    Hey, thanks for reaching out! 😊 It looks like the issue you’re encountering is due to stale or outdated data, which is completely normal when working with enrichment processes. When this happens, it means the data needs to be re-run to refresh it. For example, if your LinkedIn profile enrichment column relies on the “safe to send” formula, it may occasionally miss rows because the data it’s pulling from is no longer up-to-date. This is likely why you’re seeing gaps and receiving the “data is stale” error. To resolve this, you’ll need to re-run the table to update the data and ensure everything works as expected. One quick way is to turn off the table and turn it on again. Here’s a quick video explaining stale data: Example of stale or outdated data. Let me know if you need any further assistance! 👍

  • Avatar of Joey W.
    Joey W.
    ·
    ·

    Thanks Bo (. 🙂

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

    We haven't heard back from you in a bit, so we're going to go ahead and close things out here - feel free to let us know if you still need something!

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

    Hi Joey W.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: