When configuring a sync the source table being empty
You may have a row access policy in place. If so, your policy will need to return true when CURRENT_ROLE() = 'OMNATA_SYNC_ENGINE'
Record history retention
Omnata keeps a full record history of sync activity inside the app's internal tables. This is to enable record-level troubleshooting for syncs and runs. For large sync payloads, this duplicate copy of records can create a storage overhead and can increase sync post-processing times.
You can customize the retention period in days under Settings > Data Management > Record History Retention. In the case of long running sync runs, setting this parameter to Zero can cut overall sync run times by ~30%, however, you will only be able to view aggregated historical metrics for sync runs going forward.
Sync run timeout
If a sync or an object in a sync fails due to timeout, it can be the result of two possible timeout settings.
The timeout parameter on the individual sync.
This is configured in the Deployment step of the sync creation wizard after setting the sync schedule; the default is 240min.
The STATEMENT_TIMEOUT_IN_SECONDS setting for the Snowflake account.
This places an upper limit on the time a query can run for. The default is 2-days, but if this has been lowered, it will override the setting in the Omnata Sync application.