Want to get help faster?

Before posting

  • Make sure you're running the latest version of Metabase. See releases for the latest OSS and EE editions.
  • Ensure you're using Java 11. As we don't support currently any Java version other than that one, many errors might appear when using an unsupported Java version
  • Search for your issue in Discourse or our Github issue tracker. (Tip: use the GitHub labels to refine your search). Other people might have already encountered (and solved) your problem.

When posting

  • Include the diagnostic info. If you can't get the info, then include the Java version (running java --version in your console) and a brief description of how you're running Metabase (JAR, Docker). The more contextual information, the better.
  • Upload screenshots or videos to help people identify what's going on and where.

Are you a paid Metabase customer?

Contact us for official support.


Regarding : Disabling sync and scan for database connections


We are migrating our database to DW solution snowflake. So last month, we have added multiple connections for snowflake in metabase. After adding new database connection for snowflake in metabase we are getting extra AWS services cost of about $700. When checked, it's not coming from Dataware house usage its coming from metabase sync and scan queries which get triggered abnormally.

We want to disable both sync and scan but looks like its already disabled but somehow still getting triggered. Attaching the screenshot for reference.

We are running metabase on ECS cluster as container service. We are using image name: "Docker" which means it's running on latest metabase image.

We are having multiple dashboards and cards on metabase which need to be migrated to snowflake but if we can't solve this issue then we can't use metabase as our BI solution.

We need your help to fix the issue ASAP. Let me know, if you need more info from our end.

@flamber can you please help here ?

with all due respect:

  1. please create a new thread
  2. you haven't posted the diagnostic info
  3. snowflake charges you by usage, if you send more queries, snowflake will charge you more
  4. you mention the word "abnormal", which for different people means completely different things
  5. seems like you need urgent support, as you posted 4 hours ago, please state so and send your question to our support email if that's the case. Consider that only paying customers access urgent support