Prior to 4/4/2021, if you toggled a new table within Heap, it became part of the regular scheduled sync and thus would sync the data alongside your currently synced tables. This would cause problems on how long it took Heap data to fully sync because it added more data to sync with the initial tables. Because of this, on 4/4/2021 we updated how we do initial table syncs to prevent this delay from happening in the future.
Our new process separates the initial table syncs from the regularly scheduled syncs. When you enable a new table, the initial table syncs materialize in the background so as not to interfere with your currently scheduled tables. The warehouse downstream won’t see this new table until it has finished backfilling. When it finishes the initial sync, it will push the data to your Heap Connect warehouse and become a part of the regular scheduled sync. This reduces the potential for a sync delay.
You can always monitor the progress of your initial table syncs in Heap. When you navigate to Integrations > Directory > hover over the toggle next to the table name, where a message will appear saying the table is pending initial sync. Once the initial sync has finished, the table will join your regularly scheduled syncs as part of the process.
For questions, reach out to support@heap.io.