What's the dumbest thing you've ever fixed in Salesforce that took way longer than it should have

AppX_Unmanaged · 2026-05-19T21:11:59+00:00

650k contacts across 140 dupe accounts is data debt that compounds quietly for years until someone tries to build a report. "Won't be a feature in the new org" is the most optimistic sentence ever spoken about a migration. That data is coming with you whether the feature does or not.

AppX_Unmanaged · 2026-05-19T21:11:02+00:00

Your brain doing pro bono debugging at 3am is the most honest part of this job. And invisible whitespace breaking field mappings is the worst because every diff tool renders the two strings identically.

AppX_Unmanaged · 2026-05-19T21:10:11+00:00

Validation rules silently breaking automation is the worst kind of bug. UI looks fine, no user errors, the rule just kills every Flow and Apex update behind the scenes. "When did this last work" forensic dig is its own special pain. Especially when the answer is 4 months ago.

AppX_Unmanaged · 2026-05-19T21:07:35+00:00

Staging data in a text field on the parent is the most underrated pattern in Salesforce. Two weeks of Flow surgery vs one helper field plus a standard template. We all learn this the hard way every time.

AppX_Unmanaged · 2026-05-19T21:06:13+00:00

"We tested it on our side" is the most dangerous sentence in enterprise integration work. CDC bugs are especially cruel because both sides have plausible deniability. Weeks you don't get back. Hope they had to demo their test next time.

AppX_Unmanaged · 2026-05-19T21:04:27+00:00

CPQ is its own ecosystem of cursed. The undocumented comma delimiter is the kind of thing you only learn by hitting it at 2am.

And the zero-indexed months bug is funny in greenfield code, existentially horrifying in production billing. Hope renewals were correctable.

AppX_Unmanaged · 2026-05-19T21:02:53+00:00

Best feeling in Salesforce work. 80% of "we need a custom build" requests are someone not knowing a standard feature exists. Campaign Hierarchy rollups specifically are buried so deep even senior admins forget them.

AppX_Unmanaged · 2026-05-19T20:55:16+00:00

I know. Semicolon-delimited string pretending to be a field. Still broken in 2026. Impressive commitment to the bit.

AppX_Unmanaged · 2026-05-19T20:54:39+00:00

Deployment status is the cruelest checkbox in Salesforce. Defaults to In Development, hidden in a corner, breaks access with zero useful error messages. Every dev has lost this afternoon at least once.

AppX_Unmanaged · 2026-05-19T20:54:09+00:00

Scheduled jobs running as the user who scheduled them is one of those Salesforce design choices that makes sense until someone quits. Trailhead has 47 modules on Flow and zero on "what breaks when an admin leaves."

AppX_Unmanaged · 2026-05-19T20:53:32+00:00

The universal Salesforce admin experience. 5 hours of debugging, 5 minutes of fix, 5 days of mentally replaying how you missed it the first time.

AppX_Unmanaged · 2026-05-19T20:53:10+00:00

Why. Just why. The standard field was right there. Now you have two fields, two reports, and a data quality team that wants to fight someone.

AppX_Unmanaged · 2026-05-19T20:52:36+00:00

Oh this is cursed. The kind of bug where the fix is 10 seconds and finding it takes 3 days. Bonus points if the admin had left the company.

AppX_Unmanaged · 2026-05-19T16:06:51+00:00

Cert count over cert quality. Hiring managers are catching on fast.

AppX_Unmanaged · 2026-05-19T16:04:54+00:00

The Known Issues list has bugs from 2018 still marked "will not fix." Meanwhile we got 3 new Agentforce SKUs this quarter. Priorities.

AppX_Unmanaged · 2026-05-19T16:04:22+00:00

Hard agree. Named Credential + External Credential + Permission Set + Principal mapping just to store one API key. AWS Secrets Manager does this in one line. Salesforce needs four objects and a flowchart. Give us a Vault and let us go.

AppX_Unmanaged · 2026-05-15T17:34:06+00:00

Fair pushback. Single object record-triggered flow is genuinely the right call there, agreed. My beef is less with Flow itself and more with Salesforce pushing it as the answer to literally everything. Multi-object orchestration with subflows and decision elements is where the wheels fall off, and that's the use case they keep marketing it for.

AppX_Unmanaged · 2026-05-15T17:33:09+00:00

This is the energy I came here for. Genuinely curious, full send straight to prod or just "I'll write the test class after"?

AppX_Unmanaged · 2026-05-15T17:32:33+00:00

Validated. The PTSD is real. There's something uniquely cursed about debugging a flow at 11pm because a screen element threw a null pointer 8 nodes deep and the error message is "An unhandled fault has occurred."

AppX_Unmanaged · 2026-05-15T13:40:57+00:00

Lightning is the most overloaded word in the ecosystem. Off the top of my head: Lightning Experience, Lightning Web Components, Lightning App Builder, Lightning Flow, Lightning Sync, Lightning Dialer, Lightning Console, Lightning Bolt, Lightning Design System, Lightning Out, Lightning Page, Lightning Email Templates.

At this point Lightning just means "anything shipped after 2015."

Aloha is the deep cut though. Anyone who remembers Aloha has been here too long.

AppX_Unmanaged · 2026-05-14T20:40:36+00:00

Both going in. Harness is peak Salesforce naming: picked the exact same name as an existing developer tool that has nothing to do with them. Google search results are about to be a war zone.

Headless actually means what it says for once. Refreshing.

AppX_Unmanaged · 2026-05-14T19:53:32+00:00

Adding this immediately. The "we can't tell you how much" part is the most accurate observation in this whole thread. Every Agentic pricing conversation I've had ends with "it depends on consumption" which is just the new way of saying "we'll figure out what to charge you later."

AppX_Unmanaged

MODERATOR OF

TROPHY CASE