Scott J.

Good morning! Sorry I posted on the wrong channel yesterday - just fatigue, we rolled a ton of changes yesterday. Anyway - to get past the error I rehydrated the missing table and the MCPs appear to have started working again. So I think perhaps I just need better guidance on how to gracefully deprecate tables when people have access to them and try to reconnect via the persistent MCP connection

I can attach in single mode

Is there a way to reset my workspace? it seems like it's attaching in workspace mode but because it can't reconnect to that database, it blocks everything else

no change - I'm using the web mcp, no default database string, I don't understand how it's getting assigned to a dead database

I can't run a DETACH because the error comes first

I can't seem to shake free from it and two other people are having the same issue

That's what I get back from Claude

⏺️ The error is: ▎ Catalog Error: Catalog 'also_analytics' has been deleted It seems like a database called also_analytics was previously attached to your MotherDuck session but has since been deleted. This is blocking all queries from executing since MotherDuck tries to load it on connection. You may need to detach or remove the reference to also_analytics in your MotherDuck account. You could try: 1. Going to the MotherDuck web UI and checking if also_analytics appears in your attached databases 2. Or running a DETACH also_analytics command to remove the stale reference Want me to try running a DETACH via the read-write query tool?

I don't know which mode, perhaps that's the issue. we didn't delete any my_db databases, but several clients seem to have picked also_analytics on their own (unless we inadvertantly made them do it via claude - maybe alphabetical?)