We're noticing a variety of errors from Fivetran that are all seen to be as false positives. Some are about cluster key errors, others about tables not existing.

When looking in the query history, I see an error about a table not existing and then there will be a query that follows that to create the table. From this, it leads me to believe the code is first attempting to make a change and then catches it as an excpetion to then create the resource. To me this is backwards and instead there should be some kind of IF EXISTS query ran to understand if a step should be completed or not.

We are seeing similar things for a bunch of tables around account level platform logs (for the Fivetran Platform Connector) that show up as the connector being used is not set to track account level details (teams, MAR, etc.). Again, these are all errors that should not be errors in the first place.

I would suggest the underlying code be revised to prevent these false positive errors from showing up in our query log history as errors that we now have to ignore.