Bo (.

You’re connecting with mohamed.almagdy@slaes-elephant.com, but you’re asking us to check mohamed.almagdy@sales-elephant.com — please make sure to use sales, not slaes.

I’d delete that from the public channel, but yes — I can access your account on my end using our admin system (not your password). If it were blocked, I’d see the same blocked message. Your account is fully active and working fine.

Hey Mohamed,

I checked your account, and the email mohamed.almagdy@sales-elephant.com is fully accessible — there are no active blocks or restrictions on our side.

If you’re still running into issues, it might be tied to another login email or a local browser problem. Try clearing your cache and cookies, then log in again using a different browser. You can also send us a short video showing how you’re signing in with this domain using the password method (just be sure not to show the password). You can share it privately if you prefer.

Everything should be working correctly on our end.

Let me know if you have more questions.

Okay, I see. No worries. Unfortunately, it’s not possible to use lookups on those properties since they’re fixed in our database and mapped internally. This has come up before as feedback, though, so it’s definitely on our radar.

Thanks for flagging it.

Hey, I get that this table isn’t working right now. What I meant earlier is that you mentioned it worked before — could you share which previous table that was?

The “Property Size” and “Revenue” columns are fixed setups, so they don’t usually accept dynamic values from a lookup like this. Knowing where it worked before will help us check what’s changed.

Let me know once you’ve got that link.

Hey, looks like this is just stale data. You can fix it by rerunning the affected rows — that’ll refresh the lookup and pull the values through again.

A quick way to do it: click the plus icon at the top of the column to manually refresh all inputs. Whenever a merge or lookup column isn’t updating, it’s almost always because the data hasn’t refreshed yet.

Let me know if you have more questions.

We detected other emails that were being linked to this account. We’ve been experiencing increasing spam usage of our free credits on the trial, so we recently implemented some robust security measures against this as we grow!

Unfortunately, we won't be able to unlock this email for you but if you have one that you've used previously that is locked, let us know and we can unlock it for you.

Hey,

I get it. The catch is each enrichment also creates a verification column. So if you set up 11 enrichments, they count as 22 columns in total, which puts you over the limit even if it looks like you’re under.

Let me know if you have more questions.

Hey,

You’re seeing “waiting for its inputs” because the formula column depends on MDB check and DNC check, and those upstream cells didn’t finish or didn’t pass a run signal. Rerunning those inputs first will let the formula evaluate correctly.

What’s happening in your setup is three interdependent columns with layered conditions are firing out of order. The normalized domain feeds company domain, which both MDB check and DNC check depend on, and your formula also depends on normalized domain. If normalized domain doesn’t complete, everything downstream can look stale and the formula stays unchecked.

Quick fix:

This can feel like a bug, but it’s mostly dependency timing. We’re working to make these chains more resilient. In the meantime, keeping the column order clean and rerunning normalized domain first will unblock it.

Let me know if you have more questions.

Hey Peter,

Thanks for the detailed video — super helpful. Here’s what’s going on and how to get this working cleanly:

1. Why your current flow breaks

1. The “Find People” search doesn’t respect row-level run conditions. Each new company can retrigger the whole search set, so your conditionals and sequential checks won’t line up.

2. Circular references in Clay aren’t just possible; it’s better to work in a linear workflow (not A → B → A but A → B → C).

3. It’s not possible to delay actions in a way that would catch everything from the Find People search. Because of that, using lookups to coordinate between tables becomes brittle, and the chain stalls or misfires.

2. What to use instead

1. Switch to the “Find Contact at Company” search. It runs at the row level, supports run conditions, and lets you control execution the way you want.

2. You can also use the custom “Find People” waterfall, which hits multiple providers while still keeping row-level control.

3. Reshape the workflow

1. Avoid circular flows (Table A → Table B → back to Table A).

2. Make it linear: Table A → Table B → Table C. That keeps dependencies clear and lets your run conditions work as intended.

Let me know if you have more questions.