Salesforce DictionarySalesforce Dictionary

Salesforce Dictionary

The most comprehensive plain-English glossary of Salesforce terms. Built by admins, for admins, devs, and consultants.

Dictionary

A–Z index
Acronyms
Compare terms
Pillar guides
Errors
How-to guides
Snippets
Reference
Contribute a term

Tools & Games

Crossword
Org Organizer
Data & queries
Apex code
IDs & naming
Setup & productivity
Salary calculator

Learn

Blog
News
Setup paths
Learning paths
Releases
Cert practice
Interview Q&A
Salary calculator
Term Flash Cards
Quiz Whiz Challenge

Community

Activity feed
Leaderboard
Members
Study cohorts
RSS feed

More

About
Mobile app
Contact
Privacy policy

© 2026 Salesforce Dictionary · An independent reference. Not affiliated with Salesforce, Inc.

Updated dailyv4.3

100 live entries · hand-written · curated

Salesforce errors,
finally explained.

One page per error string. Plain-English cause. How to actually fix it - written by hand, no AI slop.

Try

Browse by category

100 errors across 11 categories. Tap a category to filter, or just search above.

100 errors

Apex

The Apex job named "<name>" is already scheduled for execution

You called `System.schedule(name, ...)` with a name that's already in use. The platform refuses duplicate-name schedules. Either abort the existing one first, or pick a unique name (e.g., suffix with timestamp).

Apex

System.AsyncException: Future method cannot be called from a future or batch method

You called an `@future` method from inside another `@future`, batch, or queueable. Salesforce blocks recursive async chains because they could spiral into infinite job creation. The replacement is `Queueable` Apex, which can chain itself.

Apex

System.CalloutException: Read timed out

The HTTP callout exceeded its allowed read time waiting for the remote server's response. Salesforce caps a single callout at 120 seconds (default 10), and total callout time per transaction at 120 seconds.

Apex

System.DmlException: Insert failed (or Update / Upsert / Delete failed)

A DML statement (insert/update/upsert/delete) failed. The exception message contains a "first exception on row N" line that tells you which record blew up and why — that's where you actually look.

Apex

Initial term of field expression must be a concrete SObject: <type>

You wrote `someThing.Field__c` where `someThing` isn't a specific SObject type — usually an `SObject` or `Object` reference. Apex needs the concrete type at compile time to resolve the field name. Cast to the specific SObject before accessing fields.

Showing 1–5 of 100 errors

Page 1 of 20