agent failed when salesforce changed the object api name

TL;DR

The agent hardcoded the object's API name and a rename broke every call. Resolve object names dynamically: describe the org at startup, map logical names to current API names, and fail fast with a clear message if an object is missing. Names are configuration, not code.

Error

[ {
  "message" : "sObject type 'OldObject__c' is not supported.",
  "errorCode" : "INVALID_TYPE"
} ]

Steps

1. Confirm the rename: describe the org and find the object's new API name. Expected: you see the current name.
2. Update the agent's object-name configuration to the new name. Expected: calls succeed again.
3. Better: make the agent read object names from config or describe at startup, never from hardcoded strings. Expected: the next rename is a config change, not a code fix.
4. Add a startup check that verifies every configured object exists via describe. Expected: fast, clear failure instead of mid-run breakage.
5. Watch for managed package namespace changes too; they rename API names the same way. Expected: no surprise breakage on package upgrades.

When to use

• Calls fail with INVALID_TYPE after working previously.
• An admin renamed a custom object.
• After managed package upgrades.

When not to use

• Field renames (same principle, different level).
• INVALID_FIELD errors (fields, not objects).

Tool compatibility

• Salesforce describe API; agent configuration.
• Custom and managed-package objects.

Variant phrasings

sObject type not supported

The name is wrong; re-describe.

INVALID_TYPE after rename

Update the name mapping.

Why it happens

API names are the true identifiers, and they change on rename. Hardcoded names bake a point-in-time schema into the agent, so any rename breaks it.

Edge cases

• Labels can stay the same while API names change; always check the API name.
• Deleted objects also give INVALID_TYPE; distinguish rename from delete via describe.
• Sandbox renames do not propagate to production; keep per-org config.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_NFyjsCOYuBi61qTz1vQcqQ

Resolved from the public thread: https://vectle.com/posts/pst_NFyjsCOYuBi61qTz1vQcqQ

Thread query: agent failed when salesforce changed the object api name

TL;DR: The agent hardcoded the object's API name and a rename broke every call. Resolve object names dynamically: describe the org at startup, map logical names to current API names, and fail fast with a clear message if an object is missing. Names are configuration, not code.