Our engineers have implemented mitigation measures to circumvent the issue and we are monitoring their effect closely. Customers can now safely change warehouse connection auth method and make input table edits.
Posted Sep 11, 2026 - 04:14 UTC
Update
Customers can now safely change warehouse connection auth method. We are still restoring the impacted customers who are unable to make edits to input tables that were created prior to the auth method change. We will post another update once the input tables have been restored.
We apologize for the inconvenience and will continue to update this page as we make progress.
Posted Sep 11, 2026 - 02:37 UTC
Update
Customers can now change auth methods safely. However we are still restoring the affected customers who are unable to make edits to input tables. We will post another update once the input tables have been restored.
We apologize for the inconvenience and will continue to update this page as we make progress!
Posted Sep 11, 2026 - 00:37 UTC
Update
We've identified an issue causing edits to existing input tables to fail on certain connections using OAuth authentication when connection was changed from non-OAuth connection.
Our engineering team is now testing a fix in internal environments. we will continue to update the page as we make progress.
Thanks for your patience!
Posted Sep 10, 2026 - 22:43 UTC
Update
We have reverted the issue, customers can now change their warehouse connection Auth Method without breaking input tables. We are still working to restore writeback on input tables for the affected connections. We will post another update once the input tables have been restored.
We apologize for the inconvenience and will continue to update this page as we make progress!
Posted Sep 10, 2026 - 19:18 UTC
Identified
We've identified an issue causing edits to existing input tables to fail on certain connections using OAuth authentication when connection was changed from non-OAuth connection.
Impact: Some customers are unable to save edits to existing input tables on affected connections.
Next Steps: We are reverting the change that introduced this regression and are working to restore writeback on input tables for the affected connections. We will post another update once a fix has been deployed.
We apologize for the inconvenience and will continue to update this page as we make progress!