SObject row was retrieved via SOQL without querying the requested field

Last updated 12 Oct 2026

What you see

Salesforce sends an email with the subject Apex script unhandled exception. Or the failed job shows in Setup, on the Apex Jobs page. The text reads like this:

Failed to invoke future method 'public static void callAddressVerify(String, List<String>)' on class 'smartystreets.AutoVerificationServices'
caused by: System.SObjectException: SObject row was retrieved via SOQL without querying the requested field: Account.BillingStreet

The field name at the end changes. It can be any address field, for example Contact.MailingStreet. The address on the record stays not verified.

Why it happens

Address Verification verifies an address as the user who changed it. It reads and writes every field of that address entry on the Data Mapping tab. When the user cannot edit one of those fields, Salesforce leaves the field out, and the verification stops with this error.

The permission set Address Verification (User) does not give access to your standard address fields. That access comes from the user's profile or from your own permission sets.

What to do

Give every user who changes addresses Read and Edit access to every mapped field. Do this for each address in the Data Mapping tab, on every object those users change.

1. Find the mapped fields. Open the Address Verification setup page. Click the Data Mapping tab. For each active address entry, note the address fields and the fields where Address Verification writes the result, for example Billing Address Status, Latitude and Longitude. See Set up the addresses.
2. Find the user in the error. The email and the Apex Jobs page name the user who ran the job. Open Setup. In the Quick Find box, type Users. Click Users. Click the user. Note the profile and the permission sets.
3. Check the field access. In Setup, click Object Manager. Click the object, for example Account. Click Fields & Relationships. Click a mapped field, for example Billing Address. Click Set Field-Level Security.
4. Give Edit access. For the user's profile, tick Visible and clear Read-Only. Click Save. If you give field access through permission sets instead, set it there.
5. Repeat for every mapped field. Check the result fields too, not only the street, city, state and ZIP code. Check the field that the error names first, but do not stop there. The missing access can sit on another field or another object.

How to check it worked

1. Change an address as one of these users, or ask one of them to do it.
2. Open the record. The address status shows verified.
3. Watch the Apex Jobs page and your email for a day. No new error comes in.

If the error still comes in, open a case. Send the full error text and the name of the profile of the user in the error.

Was this helpful?

Yes No

Related

• All Address Verification troubleshooting
• Install the newest version of Address Verification. TAF works on bugs in the newest version only.