Fivetran Release Notes

You can now choose to automatically update your time zone to match daylight saving time in the US (from the second Sunday in March to the first Sunday in November). This automatic update ensures that Fivetran begins your sync schedule at the same time we did before the time change.Daylight saving time automatic update toggleLearn more in our Destinations documentation.

Now you can use the MAR category filter both for the Daily MAR chart on the Account Usage page in your Fivetran dashboard, and for the Connector Usage page chart.usage\_chart\_free\_mar

We now support dbt Core 1.2.2 and 1.3.0. You can use these versions to run your projects.

Azure Private Link is now generally available. You can use Azure Private Link with your source, destination, or both your source and destination.Learn more in our database connection and destination connection documentation.

We have added the schema_status parameter to our Update a connection endpoint. You can use it to capture the connection schema before the initial sync. For more information, see our documentation.

AWS PrivateLink is now generally available for Redshift.For more information, see our Redshift setup guide.

Azure Private Link is now generally available for Snowflake.For more information, see our Snowflake setup guide.

We now support dbt Core 1.2.1. You can use this version to run your projects.

SAML users can now log in to their Fivetran accounts directly from the login page. If SSO is enabled for your account, you’ll enter your email on the login page, then continue logging in with SSO. If you want to log in with a password instead, you can switch to the email/password login option.

We now support dbt Core 1.1.2 and 1.2.0. You can use these versions to run your projects.

We have released custom scheduling for Transformations for dbt Core. Transformations with a custom schedule run according to the schedule you choose, except when it overlaps with the upstream connector's schedule. In that case, we wait until the connector finishes syncing to run the transformation. With custom scheduling, you can:

• Save on warehouse costs by running your transformation less frequently than your connector.
• Ensure that all upstream connections have synced when you run your transformation by matching its schedule to your slowest upstream connector.

Learn more in our custom scheduling documentation.

We have added a new check that we perform during the webhook creation or activation. The endpoint specified in the payload should exist and return a successful HTTP code. Otherwise, we will return an HTTP 400 Bad Request error.

We have added a new icons field to the Retrieve source metadata and Retrieve connection configuration metadata endpoint responses. This field contains a list of additional icon URLs in different formats (for example, .svg or .png) for the connector.

We have changed the retry algorithm for sending webhooks. We now use an exponential backoff strategy - we wait 6 minutes before the first retry, 21 minutes before the second retry, and so on. Learn more in our Retries documentation.

Fivetran has created a dbt Core-compatible app reporting model that aggregates data from our most popular app platform connectors into a unified table. This pre-built model allows you to compare your app activity by device, country, OS version, traffic source, and subscription levels.The app reporting model supports the Apple App Store and Google Play connectors.Learn more in our app reporting model documentation.

For failed syncs, Fivetran now calculates the start time of the next sync by adding a retry interval, which varies depending on the sync frequency, to the time of the sync failure.

On the connector details page in your Fivetran dashboard, we now display the Active Incident Banner for Connector Incidents and the Alerts Error side panel when there is an active high priority incident posted on our Status page.active\_incident\_banner

You can now send Fivetran notifications to any email address. Previously, you could only send notifications to other Fivetran users. Learn more in our Send notifications to any email address documentation.You can also now send Fivetran notifications to any system that accepts email-based triggers. The following systems support email notifications:

• Slack
• Microsoft Teams
• Opsgenie
• PagerDuty
• ServiceNow

Learn more in our Send notifications to third-party systems documentation.

We have implemented email notification that informs you about webhook event sending failure. To turn it on, go to Account notifications page and change the Receive an email when webhook events failed to be sent value.