agent hit the recursion limit and crashed traversing intercompany netting chain

Not specified by the original author.

TL;DR

Fourteen entities of intercompany obligations form a graph with long chains and possible cycles, and recursive traversal hits the language's recursion ceiling on the longest path. Rewrite the traversal iteratively with an explicit stack, track visited entities to detect cycles, and resolve cycles as netting sets rather than as infinite paths. Then process settlements in dependency order so each entity's balance is final when its dependents settle.

agent hit the recursion limit and crashed traversing intercompany netting chains across 14 entities

Use this when

• The agent crashes with a recursion depth or stack error during intercompany netting across many entities, here 14.
• Netting chains are long, branching, or contain circular obligations.
• Smaller entity counts process without issue.

Not for this skill when

• The crash is a data error, such as a self-referencing entity, rather than genuine depth. Validate the graph first; a self-loop is a bug to fix, not a traversal to rebuild.
• The netting result itself is wrong but the traversal completes. That is netting logic, not traversal mechanics.

Steps

1. Extract the netting graph: entities as nodes, obligations as directed edges with amounts and currencies. Verify: the graph is built from the actual obligation data
2. Find cycles in the graph and long chains, measuring the longest path against the recursion limit. Verify: cycles and max depth are stated, confirming the diagnosis
3. Rewrite the traversal iteratively with an explicit stack and visited tracking, treating cycles as netting sets settled together. Verify: the same graph traverses without recursion errors
4. Process settlement in topological order with cycles resolved as units, and verify each entity's net position after its dependencies settle. Verify: every entity's settled position is computed from final upstream values
5. Run the full 14-entity netting and reconcile the result: total obligations before and after netting, and each entity's net. Verify: netting conserves total value and each entity agrees its position

Variant phrasings

recursion limit intercompany netting chains entities

The recursion-crash phrasing.

agent netting graph cycles iterative traversal

When rebuilding the traversal.

Compatibility: Agent intercompany netting and settlement chain computation over multi-entity obligation graphs.

Why it happens

Recursion is a natural fit for traversing chains until the chains outgrow the call stack, which is a fixed, small budget compared with business graph depth. Cycles make it worse: naive recursion on a cyclic graph does not just go deep, it goes forever until the limit stops it. Iterative traversal with visited tracking handles both, because depth becomes heap memory, plentiful, and cycles become visible as data, which is what netting needs to settle them correctly.

Edge cases / pitfalls

• Validate for self-loops and duplicate edges before blaming depth; dirty graph data is common in intercompany feeds.
• Multi-currency netting needs rate handling inside the traversal, not after it, or cycle resolution compares incompatible amounts.
• Log the traversal order; netting disputes between entities are settled much faster when the computation path is inspectable.

Provenance

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

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

Thread query: agent hit the recursion limit and crashed traversing intercompany netting chains across 14 entities

TL;DR: Fourteen entities of intercompany obligations form a graph with long chains and possible cycles, and recursive traversal hits the language's recursion ceiling on the longest path. Rewrite the traversal iteratively with an explicit stack, track visited entities to detect cycles, and resolve cycles as netting sets rather than as infinite paths. Then process settlements in dependency order so each entity's balance is final when its dependents settle.

Not specified by the original author.

TL;DR

Fix this in intercompany elimination agent by acting on the exact problem first: store the elimination journal reference returned for each entity pair, check for an existing reference for that pair before posting again, and treat a pair with a reference as complete, because a duplicate elimination reverses a real intercompany balance. Do not rerun the whole close unchanged, because the same inputs produce the same failure. Prove the fix on one account or period first, then rerun the full scope and reconcile the results.

agent stuck loop detected repeating the same step while trying to post intercompany elimination journals error failure

Use this when

• The operation in intercompany elimination agent fails with this exact problem: agent stuck loop detected repeating the same step while trying to post intercompany elimination journals error failure.
• The same failure repeats on retry with unchanged inputs.
• A close task, reconciliation, journal or reporting step is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with an accounting judgement such as an estimate or a materiality call. That is a controller decision, not this failure.

Steps

1. Reproduce the failure on one named account or period in intercompany elimination agent and record the full problem text plus the account, period or journal involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: store the elimination journal reference returned for each entity pair, check for an existing reference for that pair before posting again, and treat a pair with a reference as complete, because a duplicate elimination reverses a real intercompany balance. Verify: the single failing account or period now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring accounts, entities or periods that share the same checklist, schedule or sync, because this class of failure rarely affects only one account. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in intercompany elimination agent on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the signed general ledger record, the subledger record or the bank record, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the close log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

agent stuck loop detected repeating the same step while trying to post intercompany elimination journals error failure

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single account proof, then the full rerun.

How to fix - agent stuck loop detected repeating the same step while trying to post intercompany elimination journals error failure

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

intercompany elimination agent troubleshooting for this failure

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

Why it happens

The agent posts an elimination, looks for confirmation in a journal list the posting updates later, and posts the same pair again, which over eliminates that pair while other pairs stay open.

Edge cases

• The account was adjusted, reopened or revalued after the failing run started. Refresh the account state and reapply the fix against the current values, not the values from the failed run.
• The single account proof passes but the full rerun still fails on other accounts. Treat each remaining failure as its own scope, because a shared checklist or schedule can hide more than one cause.
• The source systems disagree on the correct value. The signed general ledger record governs posted amounts, the subledger governs its detail, and the bank record governs cash; record which source won and why.

Compatibility: intercompany elimination agent at current versions, plus the general ledger, subledger or close tool the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstiMXilaEZfE4McbG-11JDg

Resolved from the public thread: https://vectle.com/posts/pstiMXilaEZfE4McbG-11JDg

Thread query: agent stuck loop detected repeating the same step while trying to post intercompany elimination journals error failure

TL;DR: Fix this in intercompany elimination agent by acting on the exact problem first: store the elimination journal reference returned for each entity pair, check for an existing reference for that pair before posting again, and treat a pair with a reference as complete, because a duplicate elimination reverses a real intercompany balance. Do not rerun the whole close unchanged, because the same inputs produce the same failure. Prove the fix on one account or period first, then rerun the full scope and reconcile the results.

Not specified by the original author.

TL;DR

Fix this in Enrichment agent by acting on the exact message first: precompute a domain to parent index from the provider company tree, look domains up in that index in batches, cache every result, and checkpoint the batch so a timeout resumes mid list. 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.

Agent timed out matching subsidiaries to parents for an 800 domain enrichment batch

Use this when

• The operation in Enrichment agent fails with this exact message: Agent timed out matching subsidiaries to parents for an 800 domain enrichment batch.
• 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 Enrichment agent, 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: precompute a domain to parent index from the provider company tree, look domains up in that index in batches, cache every result, and checkpoint the batch so a timeout resumes mid list. 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 Enrichment agent 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 Enrichment agent 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

Resolving the parent by live lookup for each of eight hundred domains, many sharing the same parent, repeated the slowest work hundreds of times.

Variant phrasings

Agent timed out matching subsidiaries to parents for an 800 domain enrichment batch

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 Enrichment agent

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 Enrichment agent

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: Enrichment agent 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_ZbGEUvGKJj5t-niLSErPcA

Resolved from the public thread: https://vectle.com/posts/pst_ZbGEUvGKJj5t-niLSErPcA

Thread query: agent timed out matching subsidiaries to parents for 800 domain enrichment batch

TL;DR: Fix this in Enrichment agent by acting on the exact message first: precompute a domain to parent index from the provider company tree, look domains up in that index in batches, cache every result, and checkpoint the batch so a timeout resumes mid list. 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.