Ajjit N.

Apologies was putting out a few fires yesterday, but everything now seems to be operational. It was a sync schedule issue which is now fixed

We have mostly confirmed that this is an issue on the Estuary side with sync schedules and reporting delays on their dashboard, will fully confirm at ~12:50 PM EST.

^Update this could be an estuary issue with sync schedules but they are not sure and are looking into it. In theory there should be a materialization update at 12:55 PM EST even if there are sync schedule issues. If that doesn't happen, then its definitely a hung materialiation like last time. I can give you an update then by the latest!

Sounds good and thanks! I've also raised this issue in the estuary slack channel

I still have access enabled to the S3 bucket for the Motherduck team so would appreciate some investigation, also happy to bring this up with the estuary team

Connor C., a few of my pipelines seem to have hung again last night. I restarted the tasks on Estuary and upgraded to Jumbo compute instances which fixed it temporarily. But as of today morning they seem to be hung again

Awesome! I will try restarting the one materialization that is still giving me issues.

Also realize this may not be an issue after the weekly release, roughly when can we expect that? Happy to wait if its just a day or two.

Connor C., we ran into this issue again in 2 more of our materializations today morning. Our usual fixes of stopping/restarting the materialization and bumping up the service accounts to jumbo do not seem to be working. So not sure what's happening.

Hey Adam E. yeah that would be great! I am not a front end developer but this does seem like the right use case