Anyone experience delays with loading — does Clay also lags for you? For example when doing the Multiple Row Lookup in one table to other table column selection doesn’t show up properly (can’t see all of the columns names listed in the dropdown).
The lag and incomplete column names you're experiencing might be due to performance issues when working with large tables or complex workflows. This can cause latency, especially when multiple actions are running simultaneously. To troubleshoot: 1. Try a hard refresh: • Mac: Command (⌘) + Shift + R (Chrome/Firefox) or Option (⌥) + Command (⌘) + E (Safari) • Windows: Ctrl + Shift + R 2. If the issue persists, it could be related to table size or workflow complexity. Large tables or tables linked together in a workbook are more likely to experience performance issues. If these steps don't resolve the problem and you need further assistance, please request human support by clicking on "Talk to a person" in this chat.
Really sorry about that. Did you notice anything specific about the columns that aren’t showing—like their field names or types? When I check the Multiple Row Lookup you added, I’m seeing four columns there, and the same four in your main table. If something’s still missing, let me know and I’ll take another look.
It again seemed to be text formatting somehow… seems to be the bug still isn’t resolved?
Hey Alex, do you mind sending a screenshot or recording of the issue you're referring to? I'm only see a single row lookup in your table instead of a Multiple Row lookup.
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.
Hi Clay team 👋
If I had to guess, I think it might be something due to text formatting but not sure since everything looks correct.
After CTRL + R and 5 seconds of waiting, it showed wrong field was mapped (even though I had mapped it correctly) - now it works again. 😅