This message was deleted.
# secoda-support
w
This message was deleted.
b
example
e
This is likely because of a bug that happens when our search index update job is running in the background and hasn’t completed when you’re viewing your search page. I’m assuming this happens when you update a description on one of your resources, or is it just random?
b
I think the only thing I did was add some of the resources to a collection. And it’s not just the search page, it’s also the catalog (but I suppose both of them may be impacted by the same bug)
What is the resolution for the bug? Rerun the extraction maybe?
Note: I can still see these tables in the collections I added them to. I can even click into these tables to see details. But theres no way for me to find tables that are not already saved in the collections
e
You’re correct, they are both impacted by the same bug. To resolve the issue, I’d recommend clicking into one of the tables on the collection and update the description. If you wait ~1min after doing that your tables should appear in the catalog. If they do not let me know and I’ll take a deeper look into the issue
I checked our Elasticsearch indices for your workspace, and it looks like the tables are populated now. Let me know if you’re able to see them on the frontend
b
Yep, all looks good now. Thanks! Also thanks x2 for being so responsive. Apologies for posting things back to back but I’m just eager to get this to a state to share with the rest of my team. I think it could be valuable in closing the knowledge gap between our team and stakeholders. 🙏
e
Alex, no need to apologize about posting things back to back. The feedback on the product helps us more than you can imagine, so don’t ever hesitate. Happy to hear Secoda could be valuable to your team and stakeholders!