Since approximately 18. 8. 2025 22:00 we're seeing sporadic errors of Snowflake transformation ending with Internal error. These issues appear to be linked to a recent underlying change in the Snowflake database, specifically affecting queries that use CREATE VIEW statements with computed columns. The error may occur across any stack.
If your transformation is using a query similar to this:
CREATE OR REPLACE VIEW TEST_W AS SELECT concat("id", 'TEST','TEST') AS id FROM TEST;
and fails with an Internal error, the following workarounds may resolve the issue:
Use a table instead of a view:
CREATE OR REPLACE TABLE TEST_T AS SELECT concat("id", 'TEST','TEST') AS id FROM TEST;
Explicitly cast the computed column to a valid VARCHAR length:
CREATE OR REPLACE VIEW TEST_W AS SELECT concat("id", 'TEST','TEST')::VARCHAR(16777216) AS id FROM TEST;
Additional Notes:
Transformations already using CREATE (OR REPLACE) TABLE statements are not affected.
Transformations that do not use computed columns, or that cast computed columns explicitly, are also unaffected.
If you're uncertain whether your transformation is affected (we fully acknowledge that the error message is not informative), please don’t hesitate to reach out to our Support team. They’ll help confirm whether this issue applies to your case.
We’re actively collaborating with Snowflake to resolve the problem. In parallel, we’re investigating potential fixes on our platform to mitigate the impact.
We sincerely apologize for the inconvenience and appreciate your patience.
Next update will be provided in 4 hours.
Update: 19.8.2025 13:40 UTC: We're actively working on this with Snowflake, but we don't have an estimated timeline for results yet. Next update will be provided in 4 hours.
Update: 19.8.2025 17:24 UTC: We have confirmed that the root cause of this is an unexpected side effect of a change in a recent Snowflake release. Next update will be provided 20.8.
Update: 20.8.2025 13:30 UTC: Snowflake is working on reverting the change for affected accounts. Next update will be provided 21.8.
Update: 21.8.2025 07:25 UTC: The change was gradually reverted on Snowflake side, we have observed no occurrences of this issue approximately since 20.8. 19:00. This means that the incident is resolved and we will continue working with Snowflake on how to re-enable the change in future in a safe way.
]]>
