<@ULVA73B9P> I received the follow error from a fa...
# ask-marvin
c
@Marvin I received the follow error from a failed flow. Can you tell me what it means and how to fix is?
Finished in state Failed("Flow run encountered an exception: ProgrammingError: 100078 (22000): Uncaught exception of type 'STATEMENT_ERROR' on line 4 at position 0 : DML operation to table DEFENDER failed on column DESCRIPTION with error: String 'An attacker might be attempting to perform NT LAN Manager (NTLM) hash cracking to access a network service. NTLM hash cracking involves a third-party intercepting NTLM authentication communication bet...' is too long and would be truncated"
m
thought for 42.2 seconds
Short version: your flow tried to insert a string into the
DEFENDER.DESCRIPTION
column that’s longer than the column’s defined maximum. The database blocked the insert rather than silently truncating it. Why it happens - The error is from Snowflake-style DML: the value for
DESCRIPTION
exceeds the column’s VARCHAR length (e.g., VARCHAR(255), VARCHAR(500), etc.). Ways to fix it (pick one) 1) Increase the column size (preferred if you want to keep full text) - See current definition:
Copy code
DESC TABLE DEFENDER;
- Enlarge the column (example to 4000 chars):
Copy code
ALTER TABLE DEFENDER
  ALTER COLUMN DESCRIPTION SET DATA TYPE VARCHAR(4000);
- Or allow Snowflake’s max (no length specified, up to 16 MB):
Copy code
ALTER TABLE DEFENDER
  ALTER COLUMN DESCRIPTION SET DATA TYPE VARCHAR;
Docs: Snowflake ALTER TABLE, Text (STRING/VARCHAR) 2) Truncate the value before insert (if you’re okay losing overflow) - In SQL:
Copy code
INSERT INTO DEFENDER (...)
SELECT ..., LEFT(description, 4000)
FROM ...;
- In Python/Pandas before loading:
Copy code
df["DESCRIPTION"] = df["DESCRIPTION"].astype(str).str.slice(0, 4000)
3) If you’re loading with COPY INTO (not regular INSERT), you can set TRUNCATECOLUMNS=TRUE on the file format to auto-truncate long strings: Docs: COPY INTO options (TRUNCATECOLUMNS) Next steps - Can you confirm you’re writing to Snowflake and share the current definition of
DEFENDER.DESCRIPTION
(run
DESC TABLE DEFENDER;
and paste the row)? I can suggest the exact ALTER or truncation approach based on that.