Fivetran: Samsara connections are currently failing with 'IllegalArgumentException: Schema and name must not be null' error
View the provider incident record →Current answer
Fivetran experienced a minor incident: Fivetran: Samsara connections are currently failing with 'IllegalArgumentException: Schema and name must not be null' error. Resolved on Sep 17, 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
Samsara
Incident Timeline
Resolved
This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connectors are syncing successfully.
Incident Summary
Description:
We identified an issue affecting Samsara connections that caused syncs to fail with the error: 'java.lang.RuntimeException: java.lang.IllegalArgumentException: Schema and name must not be null' .
Timeline:
This issue began on Sep 16, 2026, at 6:24 PM UTC and was resolved on Sep 16, 2026, at 11:10 PM UTC.
Cause:
The failure was caused by an issue in the schema migration code introduced during a recent rollout.
Resolution:
We implemented a fix to address the schema migration issue, after which syncs began succeeding again.
Incident Summary
Description:
We identified an issue affecting Samsara connections that caused syncs to fail with the error: 'java.lang.RuntimeException: java.lang.IllegalArgumentException: Schema and name must not be null' .
Timeline:
This issue began on Sep 16, 2026, at 6:24 PM UTC and was resolved on Sep 16, 2026, at 11:10 PM UTC.
Cause:
The failure was caused by an issue in the schema migration code introduced during a recent rollout.
Resolution:
We implemented a fix to address the schema migration issue, after which syncs began succeeding again.
Sep 17, 2026 at 12:38 AM UTC
Monitoring
We’ve implemented changes related to schema migration, and syncs are now succeeding. We’re continuing to monitor the connections
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
Sep 16, 2026 at 11:51 PM UTC
Identified
We’ve identified the cause of the connection failure and are actively investigating further. The issue appears to be related to a schema migration failure, which is preventing the connection from completing successfully. Our engineering team is working on a fix.
Sep 16, 2026 at 11:38 PM UTC
Identified
The issue has been identified and we are working to resolve it.
Sep 16, 2026 at 9:00 PM UTC
Was your business affected by this Fivetran outage?
Follow Fivetran and route available status alerts to email or a team channel.