The sync latency is a significant detriment to this product.
We spend a lot of time fiddling with the underlying database schema (star schema structures, etc) to get the performance we need out of the front end, and to work around data presentation limitations … it seems that every change in the database schema takes some unknown amount of time for Metabase to recognize.
I read on the GutHub forum that Metabase does a length stats scan of the schema periodically to pick up new changes. There was a request that table-level sync/scan could be performed. In my case I added a new table to replace a view, the table has a different name, and I am now waiting for it to appear on the table list so I can use it for my Question. It would be nice if the table list had a “sync” or “search for new objects” button that would do a quick scan and pull the new table onto the table list. Scan for stats later.
Again it cripples our dev efforts when iteratively working on the underlying schema while building our front-end charts and reports.