Too many SOQL queries: 101
Decode Trail Latest Questions
Business rules often evolve gradually rather than changing all at once.Testing new logic without disrupting live processes is critical.Traditional Apex-based approaches make this risky.
Some queries that were once fast are now approaching timeout limits. Indexes exist, but performance gains are inconsistent. As more filters and joins are added, tuning becomes difficult. I want to understand why SOQL optimization gets harder at scale?
We noticed that a Flow works correctly when tested as an admin, but behaves differently or fails for standard users. Sometimes records aren’t updated, or certain paths don’t execute at all. There are no obvious errors shown to users. I ...
In single-org projects, small shortcuts often feel harmless and efficient.When the same solution must work across many orgs, those shortcuts quickly become liabilities.This transition forces a deeper level of architectural discipline.
Flows worked before deployment but not after. I want to understand why.
I’ve already removed SOQL queries and DML operations from loops in my Apex code. Despite that, I’m still hitting limits in real production scenarios with large datasets. The logic itself isn’t very complex, but the limits seem easy to hit. ...
We started with a few simple record-triggered Flows, and they worked well initially. Over time, more conditions, paths, and updates were added to handle new requirements. Now debugging and updating these Flows feels risky and time-consuming. I’m trying to understand ...
Tests pass, but production fails. I want to understand why
My LWC works smoothly when testing with small datasets, but performance drops noticeably with real production data. Page loads become slower and interactions lag. I’m not doing anything obviously heavy on the client side. I’m trying to understand where the ...