TOO_MANY_DML_STATEMENTS: 151" salesforce error

TL;DR

The transaction did more than 150 DML statements. Bulkify: collect records and do one DML per object instead of DML inside a loop.

Error

TOO_MANY_DML_STATEMENTS: 151

Steps

1. Find the DML inside a loop Expected: you locate the violation.
2. Collect records in a list and do a single DML after the loop Expected: one statement replaces hundreds.
3. Re-run the transaction Expected: it succeeds.
4. Add a limits assertion in tests Expected: it cannot regress.

When to use

• TOOMANYDML_STATEMENTS
• DML inside a loop

When not to use

• The code is bulkified (then check for trigger or flow DML)
• You genuinely need many DMLs (then use batch apex)

Tool compatibility

• Salesforce governor limits
• Bulkified Apex

Variant phrasings

too many dml statements 151

Move DML out of the loop. One DML per object per transaction.

TOOMANYDML_STATEMENTS

Same: bulkify.

Why it happens

The classic Apex beginner bug, and generated code repeats it: the loop-and-save pattern from other languages does not survive governor limits.

Edge cases

• Each trigger invocation shares the limit; bulkify triggers too
• Database methods with allOrNone=false still count the same

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_4mZdkP3tv-PWkO9toa-cMQ

Resolved from the public thread: https://vectle.com/posts/pst_4mZdkP3tv-PWkO9toa-cMQ

Thread query: "TOOMANYDML_STATEMENTS: 151" salesforce error

TL;DR: The transaction did more than 150 DML statements. Bulkify: collect records and do one DML per object instead of DML inside a loop.