Engineering Atlas
☰ Menu
PortfolioAtlasDeploySQLData ViewsEnvBites
PT
Engineering Atlas / Shit That Bites You in Production / LookupRows() Stops at 2,000 Rows
medium impactPRODUCTIONAMPscript

LookupRows() Stops at 2,000 Rows

A loop over LookupRows() appears to “randomly” miss records in a one-to-many dataset.

Context Pack →Open Workspace →
Trust & provenancePRODUCTION
Evidence tierPRODUCTIONOfficial sources1Other sources0Last verifiedNot recorded

Evidence tier describes my hands-on relationship with the content. Official sources describe platform contracts/documentation. Production observations should not automatically be treated as official limits.

Why it bites

LookupRows() returns an unordered rowset with a maximum of 2,000 rows.

What to check
  1. Could the lookup key match more than 2,000 rows?
  2. Does business logic actually require processing that many rows at render time?
Make it cheaper next time
  1. Use bounded lookup patterns in message rendering.
  2. Precompute large relationships in SQL or external processing instead of iterating huge rowsets during send.
ampscriptlookuprowslimitperformance
Connected knowledge

Keep following the context.

Explicit and inferred relationships from the Atlas model.

View this node in graph →
Production Bite
Personalization Can Become a Throughput Problem

Journey injection looks healthy, but email build/send throughput falls behind and queue depth grows.

Shared context: ampscript, performance, lookuprows
Snippet
Defensive LookupRows()

Handle zero-row lookups explicitly before reading row fields.

Shared context: ampscript, lookuprows
Snippet
Bounded LookupOrderedRows()

Retrieve a small, ordered rowset instead of scanning an unbounded one-to-many relationship at render time.

Shared context: ampscript, performance
Runbook
Email Personalization / Render Failure

Debug an email that fails for some recipients or builds too slowly because personalization is fragile or expensive.

Shared context: ampscript, lookuprows
Pattern
Precompute Heavy Message-Time Personalization

Move large lookups and expensive transformations out of email render time when the data can be prepared earlier.

Shared context: ampscript, performance
Snippet
SARGable Rolling Date Window

Filter recent Data View rows without wrapping the source date column in a function.

Shared context: performance
Snippet
Pre-Aggregate Tracking Before Joining

Reduce event grain before combining behavior tables.

Shared context: performance
Snippet
Stage Before Large Add/Update

Move expensive transformation into an overwrite staging DE before a large Add/Update write.

Shared context: performance
Sources / verification
Salesforce — LookupRows() ↗