Use this glossary when a Job or Payloads UI action shows an error.

Start from the Job whenever possible. The Job usually shows the request data, response data, target output, runtime metrics, and the detailed error message in one place.

The exact wording may vary between package versions and Salesforce runtime paths, but the checks below give you the right first places to look.

For the troubleshooting workflow, see Troubleshoot failed Jobs.

Payloads could not find an Endpoint for the inbound request URL.

Check the Site URL, Endpoint URL, path, namespace, and whether the Endpoint record exists.

Also check that the external system is calling the generated Endpoint URL, not the Payload record URL. This error is usually a routing problem rather than a body mapping problem.

The inbound request used a different HTTP method from the Endpoint configuration.

Check the caller's method and the Endpoint Method field. For example, a POST request will fail if the Endpoint is configured for GET.

Once the methods match, test again before changing the Payload body or Data Targets.

Payloads found the inbound Endpoint but could not resolve the related Payload.

Check that the Endpoint is linked to the correct Payload and that the Payload has a stable API Name. If the Payload was deleted or recreated, update the Endpoint rather than trying to patch the request body.

Payloads tried to load a Payload by API Name but could not find a usable record.

Check the Payload API Name, whether the Payload still exists, and whether the running user or Site Guest User has access to the required Payloads configuration.

For inbound requests, also review the Site Guest User permission set and object/field access.

A Bearer Token Credential needs a generated Credential Payload for token refresh, but Payloads could not find it.

Open the Credential and check its token Payload relationship. If the Credential was created before the current bearer-token flow existed, review it with a Payloads admin.

Users should not normally create Credential Payloads manually. The Credential setup should create the supporting Payload.

The outbound call returned a response that did not satisfy the Payload's Response Failure Policy.

Check the Response Status Code, Response Status, Response Body, and the Payload's response policy fields.

If the API uses non-2xx responses for expected business outcomes, configure the response policy intentionally and model the response body as needed. Do not ignore response statuses just to make the Job complete; make the policy match the API contract.

Payloads could not parse the body as JSON.

Check that the body is valid JSON and that the Payload's content type matches the incoming or outgoing body.

If the body came from an external caller, open the Job and compare the raw inbound body with the expected sample.

Payloads could not parse the body as XML.

Check XML syntax, declaration, doctype, processing instructions, namespaces, and whether the Payload is configured with XML as the relevant content type.

Small XML structure issues can cause parser errors before Payloads reaches any Data Target logic.

Payloads could not parse the form URL encoded body.

Check field encoding, bracket syntax, array notation, and whether the Payload is configured for form URL encoded content.

If the body includes repeated values or bracketed paths, compare the Job body with the external API's exact field naming convention.

A conversion or extraction action expected an Element key or path but did not receive one.

Check the Flow action configuration or the mapping that calls the extractor. The action needs to know which value in the structured body should be read.

The Element key or path is not in a shape Payloads can resolve.

Check for empty path segments, broken bracket syntax, missing indexes, or a path that points through a non-container value.

If the path points into an array, confirm whether the action expects a specific entry or a repeated structure.

One or more Data Target records failed, and the Payload is not configured to allow partial success.

Open the Job and review Data Target output. Check validation rules, required fields, lookup values, field-level security, duplicate rules, and target field mappings.

This usually means Payloads reached the Salesforce write step, so the useful evidence is in the target output rather than the inbound request routing.

Payloads could not refresh subscription state from the Hub.

Open Billing, refresh subscription, and review the visible error. Check connectivity, authorised environment setup, and whether billing is managed from production.

Do not edit subscription state records manually to clear the error.

Payloads could not start the Job cleanup scheduler.

Check user permissions for scheduled Apex, existing scheduled jobs, and whether the cleanup service is already running.

If cleanup is already running, refresh Home before starting it again.

For most errors, check:

If the error message contains sensitive data, redact it before sharing it outside your org. The Job often contains enough context for support, but it may also include request or response values that should not be pasted into public channels.