A constraint violation, overflow, or permission error caused the statement to fail — 3621 is the follow-up message. A trigger on the target table failed, causing the statement and trigger to roll back. A user-defined error (RAISERROR/THROW) in a stored procedure caused the calling statement to terminate

Step 1: Find the primary error — error 3621 is never the root cause. Look at the error message immediately before 3621 in the SQL Server error log or application error output.. Step 2: Fix the root cause error (e.g. constraint violation 2627, overflow 8115, permission error 229) — resolving that error will eliminate 3621.. Step 3: In ADF pipeline failure details, expand the full error stack — the first error in the list is the actionable one; 3621 is the termination notice.

Low severityquery

Power BI Refresh Error:
3621

What does this error mean?

The statement was terminated because of a previous error — error 3621 is always accompanied by the actual error that caused the termination.

Common causes

1A constraint violation, overflow, or permission error caused the statement to fail — 3621 is the follow-up message
2A trigger on the target table failed, causing the statement and trigger to roll back
3A user-defined error (RAISERROR/THROW) in a stored procedure caused the calling statement to terminate

How to fix it

1Step 1: Find the primary error — error 3621 is never the root cause. Look at the error message immediately before 3621 in the SQL Server error log or application error output.
2Step 2: Fix the root cause error (e.g. constraint violation 2627, overflow 8115, permission error 229) — resolving that error will eliminate 3621.
3Step 3: In ADF pipeline failure details, expand the full error stack — the first error in the list is the actionable one; 3621 is the termination notice.

Frequently asked questions

Why does SQL Server raise error 3621 alongside other errors?

SQL Server uses 3621 to signal that a statement was rolled back due to a prior error. It helps distinguish between statements that completed partially vs. those that were fully terminated.

Can error 3621 appear without another error?

In practice, no — 3621 always accompanies another error. If you only see 3621 in logs, check for filtered logging that may be suppressing the primary error.

Does error 3621 mean data was rolled back?

Yes — the statement that caused 3621 was terminated and rolled back. Any partial changes from that statement were undone. Prior committed statements in the same batch are not affected unless SET XACT_ABORT ON is used.

Official documentation: https://learn.microsoft.com/en-us/sql/relational-databases/errors-events/database-engine-events-and-errors