Clay Icon

Investigate Fluctuating LinkedIn Data Causing Credit Loss and Table Errors

·
·

LinkedIn data keeps fluctuating between different company names. Can you please investigate? It's costing me lots of credits, and errors in my tables

  • 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 LuisArturo
    LuisArturo
    ·
    ·

    Hey there Petra thanks for reaching out, sorry to hear you have been experiencing this. Do you mind giving a bit more information on how is the data fluctuating within the tables, have the data fields been consistently changing such as company size going from 51-200 to 201-500 and then back 51-200? Or is the data being mis-contributed to the wrong company? Also has this been occurring in tables for all of your workspaces or just in a particular workspace. As for the video you are asking to watch is it a Loom video from one of our Clay team members and if yes what is the name of the video?

  • Avatar of Petra H.
    Petra H.
    ·
    ·

    Hey LuisArturo — mostly noticing the data is miscontributed to the wrong company, and then the cell goes stale, and when I refresh it's a new company, which respectively changes the company sizes. Can you request to view the video and I can share it with you?

  • Avatar of LuisArturo
    LuisArturo
    ·
    ·

    Thank you for the additional information on this issue, are you seeing across all of your workspaces, as I see you are a part of 4 different ones or is it affecting a singular workspace in particular? Just requested access for the video.

  • Avatar of Petra H.
    Petra H.
    ·
    ·

    So far on one workspace LuisArturo -- just shared the video

  • Avatar of Petra H.
    Petra H.
    ·
    ·

    LuisArturo the video doesn't really show the issue tbh, i couldn't replicate the example

  • Avatar of Petra H.
    Petra H.
    ·
    ·

    but it happened to me yesterday and today

  • Avatar of LuisArturo
    LuisArturo
    ·
    ·

    Hey there Petra the video did show a couple instances of this happening will which was helpful, question can you confirm which table is this was occurring in from your Self-source Workbook it a little hard to see.

  • Avatar of Petra H.
    Petra H.
    ·
    ·

    The first tab in the workbook

  • Avatar of Petra H.
    Petra H.
    ·
    ·

    LuisArturo can you backfill some credits please? Not sure how much we lost, but this is the first time we're down to 5K

  • Avatar of Petra H.
    Petra H.
    ·
    ·

    Now I keep getting this error whenever I try to edit the source of the Find People column

  • Avatar of Tanvi R.
    Tanvi R.
    ·
    ·

    Hi Petra! I just requested access to your loom video as I am unable to view it. I took a look at your workbook and saw the Errored People search column. It doesn't seem to be a bug as the other find people search columns are working, but I reached out to our engineering team to further understand the issue. I just increased your column limit, do you mind trying to duplicate the column and let me know if the error continues to occur? It looks like the error is isolated to just this column.

  • Avatar of Tanvi R.
    Tanvi R.
    ·
    ·

    I've also added back 5000 credits for you :)

  • Avatar of Petra H.
    Petra H.
    ·
    ·

    Hey Tanvi R., just shared the video with you, thanks! The video is about stale data, not the people column. I'll have to follow-up on this tomorrow as I can't right now, sorry!

  • 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 Petra H.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: