This message was deleted.

I have the exact ame problem

@bright-energy-78562 & @kind-cat-96388..@elegant-house-93198 is looking into this right now. We moved some of the infrastructure and it's causing this error with the extractor.

Hey @bright-energy-78562 and @kind-cat-96388 thanks for bringing this to our attention. The problem with the scheduler has been resolved, and you should see your daily extractions show up today. There are lots of extractions queued up, so it might take a few hours but they’ll be there today

Thanks for resolving!

Hey @bright-energy-78562, just to confirm is it the Metabase and dbt integrations that aren’t running? It looks like the Postgres and Redshift integrations are running regularly now. I just wanted to confirm because it’s likely a specific issue with those two integrations.

Metabase, Redshift, and dbt don’t appear to be running on daily (based on the “History” tab)

It was likely a UI thing. I’ll look into the Metabase and dbt extractions now.

Tableau is also not extracting by the looks of it

Thanks for the additional context @plain-balloon-39336. Two updates on this: @bright-energy-78562 we’ve found the Metabase / dbt issue and will be shipping a fix shortly. @plain-balloon-39336 we’ve also fixed the issue you’re seeing with Tableau which will be in the next release. We’ve also revamped the extraction UI to give you more insight into what’s going on, which will also be in the next release.

Ooof not a good day for AWS 😬 thanks for the update!