This message was deleted.

Hey Ryan, we do this automatically now on the latest extractions. So if you run an extraction for Snowflake and dbt it should remove anything that Secoda does not have access to

Okay, then there's a bug somewhere. There are a lot of tables showing up in schemas that Secoda does not have access to.

I can see in our logs that there’s an extraction currently running, so I’ll double check once that extraction has run. If it continues to show these schemas/tables it doesn’t have access to I’ll remove them for you

Okay, sounds good. And here are the schemas in Snowflake

@blue-ocean-91219 it looks like those schemas are selected in your dbt integration schema list. So you’ll have to uncheck them from there

oops okay working on deleting them and rerunning now, will let you know. thanks!

Hey @blue-ocean-91219 apologies about the delays on the response. I’ve been OOO since June 16. I’ll be looking into this issue today

hi @elegant-house-93198, great thanks! I am still seeing this issue today

Hey @blue-ocean-91219 it looks like our stale data detection is not working for those particular schemas. We can manually remove the tables that aren’t associated with the schemas above. I’ll just send you an excel of the list of tables so you can confirm before we remove them

sounds good

Hey Ryan, could you let me know if the tables are gone now? We pushed another update that should have fixed it.

yes, they're gone! thanks!