Skip to main content
Scheduled reads stopped running
Reads paused after repeated failures. Check the connection, then unpause via API.
read
Proxy call returns 429 Too Many Requests
Use throttle mode and the retry-after headers instead of hammering the provider.
proxy
Webhook receiver rejects large payloads
Payloads reach 300 KB, so raise your body-size limit or switch to URL delivery.
webhooks
Connection shows bad_credentials
The customer’s credentials are no longer valid, so have them re-authenticate.
auth
Async write accepted but the record is missing
Accepted is not applied. Check the operation’s status and logs.
write
Salesforce read: No such column error
The connected user lacks field-level visibility, or the field name is wrong.
read
Salesforce write: No such column error
The field doesn’t exist in the customer’s org, or the user can’t see it.
write
Salesforce subscribe fails with LIMIT_EXCEEDED
Salesforce allows Change Data Capture on 5 entities by default. Reduce objects or add the license.
subscribe
Salesforce subscribe events don’t fire for a field
Salesforce only emits change events for direct fields, not derived ones like LastActivityDate.
subscribe
Salesforce connection turns bad_credentials
Missing refresh_token scope, a reused app, an expiring token policy, or revoked access.
auth
Salesforce returns INVALID_SESSION_ID
Check the connection’s scopes, app reuse across projects, and duplicate connections.
auth
Salesforce read: too many junction ids
EmailMessage junction lookups exceed 500. Drop the ID fields or read EmailMessageRelation.
read
Salesforce: Object type is not supported for a standard object
Usually an object permission gap for the connected user, not a missing object.
read
Check a customer’s Salesforce API quota
Query the limits endpoint through the proxy when you suspect rate limiting.
proxy
Salesforce (JWT) installation fails
Certificate, consumer key, and OAuth policy checks for the JWT flow.
auth
Google delegation: unauthorized_client error
Domain-wide delegation isn’t authorized for the service account’s client ID and scopes.
auth
Google delegation: invalid_grant error
The impersonated user or key is invalid. Check the connection details.
auth

​
Can’t find your error?

Email support@withampersand.com or ask in your shared Slack channel with our engineers. If you think the docs should cover it, file an issue.