Release Notes

March 2025

We have added new fields connection_id and connection_name to all log events. They will replace current fields connector_id and connector_name, which are now deprecated and will be removed in the future.

We also added a new fields in some specific events data instead of deprecated ones:

For more information, see our Logs documentation.

We have deprecated the following Transformation log events:

• dbt_run_start - replaced with transformation_start
• dbt_run_succeeded - replaced with transformation_succeeded
• dbt_run_failed - replaced with transformation_failed

February 2025

Fivetran Transformations are now generally available. You can leverage a stable, reliable, and production-ready environment to manage your transformation workflows.

See our How Does the New Transformation Flow Built Around dbt Jobs Differ From the Former Flow Built Around Output Models? troubleshooting page to learn more about the new features and and improvements.

December 2024

We have updated the format of logs and webhooks for user-defined dbt jobs and Quickstart transformations.

• Transformation Log Events
• Webhooks Events
• Fivetran Platform Connector Sample Queries

November 2024

We have removed the api_call from the log event list. Use the new event, extract_summary, instead. For more information, see our Logs documentation.

August 2024

We have added a new log event, extract_summary. For more information, see our Logs documentation.

April 2024

We no longer generate the following log events:

• STATUS (deprecated)
• DISCONNECT_BI_TOOL
• CONNECT_BI_TOOL
• UPDATE_BI_TOOL
• CREATE_STAGING_TABLE
• APPLY_TIER_LIMITATION
• MIGRATE_SCHEMA_CONFIG
• SCHEMA_MIGRATION_FAILURE
• SCHEMA_MIGRATION_SUCCESS
• DISMISS_WARNING
• TRANSFORMATION_RUN_START
• TRANSFORMATION_RUN_SUCCEEDED
• TRANSFORMATION_RUN_FAILED

For more information, see our Logs documentation.

March 2024

We have added a new log event, schema_migration_end. For more information, see our Logs documentation.

January 2024

We have removed the forced_pause_connector dashboard activity log event. We now send an automated pause event, pause_connector with the actor:Fivetran attribute. We issue the automated pause event either for broken or trial expired connectors.

December 2023

We have removed the following dashboard activity log events:

• create_file_upload_table
• merge_rows
• remove_file_upload_table
• signin_warehouse
• signout_warehouse
• upload_file

December 2022

We now generate the CANCELED sync status for the sync_end log event in our logs.

January 2022

We have added the sync_id field as a common field of the log events.

December 2021

We now generate the sync_end log event in our logs for every possible sync status:

• SUCCESSFUL
• FAILURE
• FAILURE_WITH_TASK
• RESCHEDULED

Previously, we generated the sync_end log event only for successful syncs.

September 2021

We now generate the change_schema_config_via_api log event in our logs when you change a schema sync configuration using our REST API. See our Logs documentation for details.

August 2021

We have updated the value of the log event's connector_id property. Previously, the connector_id and connector_name properties both contained the connector name. Now, connector_id contains the connector ID, while connector_name still contains the connector name.

Learn more in our Logs documentation.

December 2020

Fivetran now supports flushing dbt transformations event data to supported log services.

Each log service has a unique path for this data:

Learn more in our Logs documentation.

November 2020

We have added a new log event, diagnostic_access_granted. Read our Logs documentation for more information.

September 2020

We have added a new log event, change_schema_config_via_sync. See our Logs documentation for more information.

We have deprecated the two audit tables, _fivetran_audit and _fivetran_audit_warning. We will stop populating the tables on November 6, 2023.

You can use our Fivetran Platform Connector along with our Fivetran Platform Connector data model to recreate the _fivetran_audit table in your destination. The pre-built data model uses the data stored in the log tables to create fivetran_platform__audit_table matching the _fivetran_audit table.

October 2018

Fivetran now supports flushing dashboard activity event data to supported log services.

Each log service has a unique path for this data:

June 2018

We no longer support read_start and read_end log event values.

We can now load all of your log event data into a single column (packing).

We have added logs for the following applications:

• Adwords
• Amazon DynamoDB
• DoubleClick Campaign Manager
• DoubleClick for Publishers
• Facebook Ad Insights
• Front
• GitHub
• Google Ad Manager
• Google Ads
• Google Campaign Manager 360
• Google Sheets
• HubSpot
• Jira
• LinkedIn Ad Analytics
• Mandrill
• Marketo
• Optimizely
• QuickBooks
• Recharge
• Sailthru
• Segment
• Stripe
• Xero
• Zendesk Support
• Zendesk Chat

May 2018

You can now navigate directly to your log service from the Connection Details page of your Fivetran dashboard.

We have added logs for the following applications:

• AdRoll
• Amazon S3
• Apple Search Ads
• Amazon CloudFront
• Dropbox
• Eloqua
• Email
• Freshdesk
• FTP
• Google Cloud Storage
• HelpScout
• Intercom
• Klaviyo
• Mailchimp
• Marin Software
• Azure Blob Storage
• Microsoft Advertising
• Mixpanel
• MySQL
• Pardot
• Recurly
• SendGrid
• SFTP
• Verizon Media
• Zuora

April 2018

We have renamed the MessageEvent event to InfoEvent.

We have added two new log events:

• json_value_too_long
• skip_column

For more information, see our Logs documentation.

We have added support for logs for the following connectors:

• Braintree
• Apple App Store (formerly iTunes Connect)
• Kantata