Why is Clay Lookup Row in Other Table not showing any tables (in Table to Search) - when clearly there are multiple tables present.
Thanks for your continued help Sayli G. , but there might be a contradiction here.
Either each developer is supposed to create their own Clay API key and use it, or they should be using only one (which as the founder of the company, I would like it to be mine).
But when I made mine the default, and only Kshitij 's was remaining (but the account was deleted), it still did not work.
I still suspect there is something wrong with my account which is preventing me from creating these accounts properly.
Nevertheless, since we have been blocked on this for more than 2-3 days, it's safer for me to use Bhanu's key as a workaround until we get to the real cause of the problem.
Hey Siddhant! Can you tell me more about why you have created multiple api keys? I can see 1 of the 3 is working.
We can delete the other two and try regenerating them. Would like more context on multiple keys.
The first image - when I regenerated it.
The second when I deleted the first one and created a new one.
The third - when another team member created it (earlier) - and it works fine for him.
So there is something wrong with my account for some reason. Sayli G.
All of our workflows are completely blocked in the entire workspace because I can't create any new lookups nor can I use the existing ones.
If there is a maximum of 10 tables that can be connected in an account (or even a workbook) - that's unbelievable. Is that correct? That would be a severe limitation for something more complex.
In any case, that is not the situation here. There was an existing Lookup Row which stopped working (because it was tied to a former employee's Clay API key, and I removed the account). https://app.clay.com/workspaces/685360/workbooks/wb_0szl7g4E96GrGgZZiFm/tables/t_0szxhbeNvreWZUyED96/views/gv_0szxhbei2HgeFcq55Ji