Inbound Sync branching

Inbound syncs tend to have much simpler configuration than outbound syncs. Because they are fetching data, typically there's not many settings to chose from which could affect the way each stream is retrieved. But in situations where you could make a change that alters the output data, branching will ensure that you can inspect it in a separate output table in Snowflake before merging.

Also, the Omnata UI allows you to choose which streams of an App are part of a sync. Changing this selection can also be done in a branch.

If your branch points to the same connection as main, and there are no branch-only configuration changes, it's assumed that the same source data is being fetched. The state of each stream will be carried to the branch and maintained there, so that any incremental streams continue from the same place without impact to the main sync.

If your branch points to a different connection to main, or there are branch-only configuration changes, it's assumed that different source data is being fetched. The state of each stream will be re-initialised the first time the branch is created, but will be remembered whenever a branch with the same name is reopened.