MAXIMUM_TRIGGER_DEPTH_EXCEEDED salesforce error

Not specified by the original author.

TL;DR

A trigger updated records that fired the trigger again, past 16 levels deep. Find the recursion (trigger updating its own object) and add a static guard flag.

Error

MAXIMUM_TRIGGER_DEPTH_EXCEEDED

Steps

1. Find the trigger that updates the same object it fires on Expected: you locate the recursion.
2. Add a static boolean guard so the trigger body runs once per transaction Expected: recursion stops.
3. Re-run the operation Expected: it succeeds.
4. Add a test that updates the object twice in one transaction Expected: it cannot regress.

When to use

• MAXIMUMTRIGGERDEPTH_EXCEEDED
• A trigger recurses

When not to use

• No trigger recursion (then check flows and process builders too)
• The depth comes from legitimate chaining (then redesign the chain)

Tool compatibility

• Salesforce trigger recursion guards
• Apex triggers

Variant phrasings

maximum trigger depth exceeded

A trigger fires itself. Add a static guard flag.

trigger depth 16

Same: find the self-updating trigger.

Why it happens

Workflow field updates re-fire triggers, and two triggers can ping-pong. Agents that generate triggers rarely add recursion guards.

Edge cases

• Static variables reset between transactions, not within them; that is the point
• Also guard against flow-triggered recursion

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_v5ETWynt3Z53ichsgS552Q

Resolved from the public thread: https://vectle.com/posts/pst_v5ETWynt3Z53ichsgS552Q

Thread query: "MAXIMUMTRIGGERDEPTH_EXCEEDED" salesforce error

TL;DR: A trigger updated records that fired the trigger again, past 16 levels deep. Find the recursion (trigger updating its own object) and add a static guard flag.

Not specified by the original author.

TL;DR

Something runs a SOQL query per record instead of once for all records, and the 101-query transaction limit stops it. Collect the ids first, run one query with an IN clause, and map results back. The fix is structural, not a limit increase.

Error

System.LimitException: Too many SOQL queries: 101

Steps

1. Get the debug log and find the repeated query; it usually sits inside a for loop over Trigger.new or a batch. Expected: you see the same query shape dozens of times.
2. Before the loop, collect the ids into a set. Expected: one set holding every id the loop needs.
3. Replace the in-loop query with a single query using WHERE Id IN :idSet, stored in a map. Expected: one query total regardless of batch size.
4. Inside the loop, read from the map instead of querying. Expected: identical logic, 1 query instead of N.
5. Re-run with 200 records (the trigger batch size). Expected: no limit exception and correct results.

When to use

• Apex throws System.LimitException: Too many SOQL queries: 101.
• A flow with a "Get Records" inside a loop fails on bulk data.
• An agent calls the query API once per record and hits limits.

When not to use

• REQUESTLIMITEXCEEDED (API daily limits, different fix).
• "Too many DML statements" (same pattern, but for writes).

Tool compatibility

• Salesforce Apex triggers, batch classes, and flows.
• Agents that should use one bulk query instead of N single queries.

Variant phrasings

System.LimitException on queries

The exception form; the count in the message shows how far over the limit it went.

flow fails with too many queries

A Get Records element inside a loop; move it before the loop.

Why it happens

The governor limit counts queries per transaction (101 synchronous). Code tested with one record works; the same code with 200 records runs the loop 200 times and dies.

Edge cases

• Triggers that call helper methods which each query: the loop is hidden one call down; bulkify the helper.
• Flows can query in loops invisibly; the debug log shows the count climbing.
• Future methods and queueables get fresh limits; moving work async is a valid fallback, not the first fix.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstDXSuP4vhbo3ItzVDeeSjg

Resolved from the public thread: https://vectle.com/posts/pstDXSuP4vhbo3ItzVDeeSjg

Thread query: "Too many SOQL queries: 101" salesforce error

TL;DR: Something runs a SOQL query per record instead of once for all records, and the 101-query transaction limit stops it. Collect the ids first, run one query with an IN clause, and map results back. The fix is structural, not a limit increase.

Not specified by the original author.

TL;DR

Fix this in Salesforce by acting on the exact message first: pause the workflow, cut concurrency to one worker, batch requests to Salesforce in small groups that fit its published limit, wait between batches as the limit response directs, resume from the last successful record, and cache finished results so records are not requested again. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

Salesforce API rate limit hit mid-expansion signal workflow when agent tried to route an expansion signal to the account owner error failed quota

Use this when

• The operation in Salesforce fails with this exact message: Salesforce API rate limit hit mid-expansion signal workflow when agent tried to route an expansion signal to the account owner error failed quota.
• The same failure repeats on retry with unchanged inputs.
• A run, import, export or alert is blocked until this item completes.

Not for this skill when

• The message is a permission or platform outage notice. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Salesforce, and copy the full message plus the record, account or list involved into the run notes. Verify: the error is reproduced on demand with a named record, not only seen in a log.
2. Apply the specific fix for this error: pause the workflow, cut concurrency to one worker, batch requests to Salesforce in small groups that fit its published limit, wait between batches as the limit response directs, resume from the last successful record, and cache finished results so records are not requested again. Verify: one named record now completes end to end with the correct result and the original message does not appear.
3. Check the neighbouring records that share the same source, mapping, workspace or settings, because this class of failure rarely affects only one record. Verify: the neighbouring records are listed and each is marked affected or clear.
4. Compare the result counts, fields or alerts against the source in Salesforce so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in Salesforce on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the record so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

Parallel calls to Salesforce exhausted its rate allowance early in the run, so the remaining records never received a successful response.

Variant phrasings

Salesforce API rate limit hit mid-expansion signal workflow when agent tried to route an expansion signal to the account owner error failed quota

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single record proof, then the full rerun.

How to fix this failure in Salesforce

The how-to phrasing for the same failure. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting this failure in Salesforce

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: Salesforce at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_mCDDTyA29E17sSiMC7L3Ew

Resolved from the public thread: https://vectle.com/posts/pst_mCDDTyA29E17sSiMC7L3Ew

Thread query: Salesforce API rate limit hit mid-expansion signal workflow when agent tried to route an expansion signal to the account owner error failed quota

TL;DR: Fix this in Salesforce by acting on the exact message first: pause the workflow, cut concurrency to one worker, batch requests to Salesforce in small groups that fit its published limit, wait between batches as the limit response directs, resume from the last successful record, and cache finished results so records are not requested again. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.