Issue with Cells Showing Blank After Left-Clicking in Data Column | Clay

Issue with Cells Showing Blank After Left-Clicking in Data Column

Sometimes I'll left-click on a cell that has run to read the contents, but then the contents will blank out and then it will say 'cell did not run'. You can see here the blanks were all cells that run since I ran run first 10 rows for this column. But on every few that I click, the text would disappear and then the Cell details box would say 'Cell has not run

5 comments

Channeled
APP
·
·
When you left-click on cells that have already run, the cell contents shouldn't disappear or show 'Cell has not run'. This behavior is not typical and may indicate an issue with your table or the specific cells.To inspect cell details properly: 1. Open your table 2. Click on the cell you want to viewIf you're still experiencing this issue, it might be a bug or a temporary glitch in the system. Our team is constantly working on improving our app and fixing any issues that arise.Could you please provide more details about when this started happening and if it occurs with all cells or only specific ones? This information will help us better understand and address the issue. Sources: Inspect Cell Details New at Clay | Clay.com
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Daniela D.
·
·
Hey Pedram! Sorry about this. Happy to help✨. Could you share the table url that has those blank cells? We'll check this.
Channeled
APP
·
·
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.
Simon I.
·
·
Experiencing this issue also for the last 2 weeks on our side. Sometimes a Quick Page Refresh solves this issue