Fivetran: Tableau (Lite) connections failing with "Failed to fetch OAuth2 Token" error
View the provider incident record →Current answer
Fivetran experienced a minor incident: Fivetran: Tableau (Lite) connections failing with "Failed to fetch OAuth2 Token" error. Resolved on Oct 19, 2026.
The notice publication date does not establish the outage start. Provider resolved: .
Looking for an update now? Check the current status, or follow Fivetran for future changes.
Provider notice timeline
Affected Components
Tableau
Incident Timeline
Resolved
This incident has been resolved. We have observed that error rates are returning to normal levels, and affected Tableau connectors are syncing successfully.
Incident Summary
Description:
We identified an issue affecting Tableau connections that caused syncs to fail with the error "Failed to fetch OAuth2 Token".
Timeline:
This issue began on Oct 19th, 2026 at 15:30 UTC and was resolved on Oct 19th, 2026 at 23:00 UTC.
Cause:
This issue was caused by a recent authentication-related change.
Resolution:
We rolled back the change and deployed the fix. Following deployment, affected connections recovered automatically and are now syncing successfully.
Incident Summary
Description:
We identified an issue affecting Tableau connections that caused syncs to fail with the error "Failed to fetch OAuth2 Token".
Timeline:
This issue began on Oct 19th, 2026 at 15:30 UTC and was resolved on Oct 19th, 2026 at 23:00 UTC.
Cause:
This issue was caused by a recent authentication-related change.
Resolution:
We rolled back the change and deployed the fix. Following deployment, affected connections recovered automatically and are now syncing successfully.
Oct 19, 2026 at 11:59 PM UTC
Monitoring
We have deployed a fix for this issue by rolling back a recent authentication-related change that was causing connection failures.
We will continue to monitor all affected connectors until they resume their normal sync functionality.
Next Expected Update: 3 hours
We will continue to monitor all affected connectors until they resume their normal sync functionality.
Next Expected Update: 3 hours
Oct 19, 2026 at 11:16 PM UTC
Identified
We have identified that this issue was caused by a recent authentication-related change. We’ve rolled back the change, and the fix is being deployed now. Once deployment is complete, affected connections should recover automatically.
Next Expected Update: 1 hour
Next Expected Update: 1 hour
Oct 19, 2026 at 10:51 PM UTC
Identified
The issue has been identified and we are working to resolve it.
Oct 19, 2026 at 8:00 PM UTC
Was your business affected by this Fivetran outage?
Follow Fivetran and route available status alerts to email or a team channel.