Clay Icon
Join the Community
02 Bugs

7 comments

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

    The issue with merged columns not returning a value is likely due to how the formula was set up. The original formula assumed there would be a response for every row, which isn't always the case. This assumption led to errors that prevented the merge column from returning the desired output. To fix this, you can add extra logic to your formula. Modify it to check if the response exists before trying to use it. For example, you could use a condition like "if {{response}} exists..." at the beginning of your formula. This adjustment should allow the formula to run smoothly, only acting on response data when it's available. If you need more help with this, please let me know, and I can guide you further or you can request to talk to a person for more detailed assistance.

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·
  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

    Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.

  • Avatar of Owen C.
    Owen C.
    ·
    ·

    Hey Bjion, thanks for reaching out! Let us know if there's anything we can do to help! :)

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·
  • Avatar of Owen C.
    Owen C.
    ·
    ·

    Hey Bijon, thanks for reaching out! Quick question, does this data come from an external source on a regular cadence, or was it a one-time bulk enrichment? Specifically, for the rows where the data didn’t Run: ** Does this happen when new rows are added to the Clay table? ** Or is it a specific set of rows that consistently don’t work, even after running the entire table once? Just trying to get a clearer picture so I can help you troubleshoot more effectively! :)