Job records store what happened when Payloads ran.

Use this reference when you need to interpret a Job field during troubleshooting, reporting, or support. For the normal troubleshooting flow, start with the Job overview article and come back here when you need field-level detail.

For task guidance, see Understand Job records.

New means the Job has been created but has not completed processing. This can be normal for queued or Batch Engine work.

Completed means Payloads finished the run successfully according to the configured runtime and response policy.

Failed means Payloads encountered an error or the response policy treated the run as failed.

Status tells you where to start, but it does not explain the whole story. A Completed Job can still contain a business response you need to review, and a New Job may simply be waiting for the correct async process.

Immediate means the Payload ran in the current execution path.

Queueable means the Payload was handed off to queueable Apex.

Batchable means the Job was created for Payloads Batch Engine processing.

Firing Mode is useful when the user expected something to happen straight away but the Job is still New. Check the intended firing mode before assuming the run is stuck.

For Flow setup, see Use Payloads in Flow.

Outbound Body stores the request body Payloads built.

Outbound Headers stores outbound headers.

Outbound Parameters stores query string parameters.

Outbound Modifiers stores URL placeholder replacements.

Outbound Queries stores Data Query output used during outbound build.

Dynamic Inputs stores values supplied at runtime.

These fields let you compare the configured Payload with the actual request Payloads generated. When an external API rejects a call, this is usually the most useful part of the Job to inspect.

Inbound Body stores the body received by an Inbound or Email Handler Payload.

Inbound Headers stores inbound HTTP or email-related header values where relevant.

Inbound Parameters stores URL parameter values where relevant.

Inbound Targets stores Data Target output generated by inbound processing.

Use these fields to confirm what the caller actually sent. If a Data Target value is blank, the Job can show whether the source value was missing from the request or whether the mapping failed later.

Response Status Code stores the HTTP-style status code where one is available.

Response Status stores the status text or short failure summary.

Endpoint stores the URL or endpoint path involved in the run.

Error Message stores the detailed error message and may include stack trace detail.

Review response fields alongside the Payload's Response Failure Policy. A non-2xx response may be expected for one API and a failure for another.

Duration tracks total runtime.

HTTP Callout Duration tracks outbound callout time.

Query Duration tracks time spent querying Salesforce data.

DML Duration tracks time spent writing Salesforce data.

CPU Time, Heap Size, Query Count, Query Rows, DML Statement Count, and DML Row Count help identify Salesforce limit pressure.

Use these fields to tell the difference between a slow external API, expensive Salesforce queries, heavy target writes, or general Apex limit pressure. Do this before changing batch sizes or simplifying mappings, because the metrics usually point to the real bottleneck.

Queueable, Batchable, Async Apex Job Id, and Batch Size help identify how the Job was executed.

If a Job stays New, check whether it was intended for Batch Engine processing and whether the Batch Engine is running. For queueable work, the Async Apex Job Id can help connect the Payloads Job to Salesforce async execution.

When cleanup deletes old Jobs, Payloads rolls key counts and metrics into Job Analytics Entry records.

These records preserve daily activity and metric trends without keeping every detailed Job forever.

Job Analytics Entry fields include New Jobs, Completed Jobs, Failed Jobs, duration totals and averages, callout duration, query duration, DML duration, query counts, DML counts, heap usage, Integration API Name, Payload API Name, Entry Date, and Entry Key.

Use analytics entries for trend reporting. Use Job records for detailed troubleshooting while those records are still retained.

When using Job fields for troubleshooting, check: