Tseegi (.

Great to hear! Thanks for letting us know, and glad everything is back to normal 🎉

I've noticed successful checkpoints around ~12:50 PM EST. Do you have any updates from Estuary side?

Got it! We'll keep an eye out on it. Thanks for confirming.

Hello Ajjit N.! We see pretty consistent automated publishing (checkpoints) on our side. Could you let me know which on of your jobs do you notice the behavior (i.e. which database does it write to)? I can look into it further with that information.

Ah, thanks for confirming! Happy diving!!

Hello aaran! Can you ask the new team member to run SELECT alias, type FROM MD_ALL_DATABASES(); or SELECT database_name, type FROM duckdb_databases(); on MotherDuck UI/CLI and tell me whether <our_main_db> appears? Could you tell me exact error message and new account's name? We could take it to the dm!

Let me know if you have any questions!

Hello Ryan S.! It looks like data_jobs is a share, and you can't CREATE SCHEMA or write to shared databases. Instead, you can create a zero-copy clone of the share, and then write to it all you want. This is a metadata operation and will not incur cost. For your reference: https://motherduck.com/docs/sql-reference/motherduck-sql-reference/create-database/

That's the account I looked at. Can you confirm that database exists on your end? You can do so by calling SHOW ALL DATABASES; Are you calling the CREATE SCHEMA on that database?

Yes, but which account did you create data_jobs on? This will help tremendously with our investigation.