Frequently Asked Questions (FAQ)

These are the answers to some frequently asked questions for Cloud Data Ingestion.

Why was I emailed: “Error in CDI Sync”?

This type of email usually means there’s an issue with your CDI setup. Here are some common issues and how to fix them:

CDI can’t access the data warehouse or table using your credentials

This could mean the credentials in CDI are incorrect or are misconfigured on the data warehouse. For more information, see Data Warehouse Integrations.

The table cannot be found

Try updating your integration with the correct database configuration or create matching resources on the data warehouse, such as database/table.

The catalog cannot be found

The catalog set up in the integration does not exist in the Braze catalog. A catalog can be removed after the integration was set up. To resolve the issue, either update the integration to use a different catalog or create a new catalog that matches the catalog name in the integration.

Why was I emailed: “Row errors in your CDI sync”?

This type of email means that some of your data could not be processed during the sync. To find out the specific error, you can review the logs in Braze by going to CDI > Sync Log.

How do I fix errors for Test Connection and support emails?

• snowflake
• redshift
• bigquery
• databricks

How do I update my email alert preferences for CDI integrations?

Each integration has its own notification preference. Go to the CDI page and select the integration name you want to update. In the Notification preferences section you can update how you receive alerts regarding the selected integration.

What happens if a future UPDATED_AT gets synced with an integration?

CDI uses UPDATED_AT to decide what data is new. After a future UPDATED_AT is synced, any data prior to that future date and time will not be processed. To fix this:

1. Correct UPDATED_AT.
2. Remove any old data that’s already synced with Braze
3. Create a new integration to process that table again.

Why doesn’t “Rows Synced” match the number in my warehouse?

CDI uses UPDATED_AT to decide which records to pick up during a sync. Check out this illustration to see how it works. At the beginning of a sync run, CDI queries your warehouse to get all records with UPDATED_AT later than the previously processed value. Any record picked up at the time when the query executes will be synced into Braze. Here are common cases when a record might not be synced:

• You’re adding records to the table with an UPDATED_AT value that has already been processed.
• You’re updating record values after they have been processed by a sync, but leaving UPDATED_AT unchanged.
• You’re adding or updating records while a sync is in progress. Depending on when the CDI query executes, there could be race conditions that lead to records not being picked up.

During a sync, is the order preserved if multiple records share the same ID?

The processing order is not 100% predictable. For example, if there are multiple rows with the same EXTERNAL_ID in the table during a sync, we cannot guarantee which value will end up in the final profile.

What are the security measures for CDI?

Braze’s measures

Braze has the following measures in place for CDI:

• All credentials are encrypted within our database, and only certain employees have authenticated access to them.
• We use encrypted connections to get data to customer warehouses.
• We make requests to the Braze API endpoints using the same API keys and TLS connections that we recommend our customers use.
• We regularly update our libraries and get any security patches.

Your measures

We recommend you and your team set up the following security measures on your side:

• Restrict credential access to the minimum required for CDI to operate. This is because we need to be able to run select (and count) on the specific tables and views.
• Restrict the IPs that can access the tables to officially published Braze IPs.