A Job records a particular Payload execution: its inputs, Action results, request and response data, errors and measured performance. Use it to verify what happened during the run rather than inferring the result from the current Payload configuration.

Use the Jobs tab to filter by Integration, Payload and Status, or select a recent Job from the Payload workspace's Jobs panel.

Check the Payload, creation time, firing mode and error before inspecting individual Actions. New and Queued indicate work that has not reached a terminal outcome. Completed means processing finished; Failed indicates a recorded failure. CSV completion can include ordinary row errors, so always inspect its result counts.

The Actions panel represents the recorded execution. Select an Action to inspect its data in the centre. Expand or collapse the panels to give the details more space.

Select Start to view captured inputs when that control is available. This belongs to the Job timeline; the Start marker on the Payload configuration page is not an input editor.

Select a Query to review recorded Salesforce query data. Select a Target to inspect the attempted records and their results. Flow Actions show recorded inputs and outputs. Payload Actions expose the child execution details and published results.

Start with the earliest failed or unexpected Action. A later missing value can be a consequence of a producer that failed or returned no data.

HTTP Request and HTTP Response show the content for their part of the exchange. Use Raw or Tree where available to compare the actual body with its parsed structure, and inspect the HTTP details and status.

For Outbound, the request is sent to the external API and the response comes back from it. For Inbound, the request comes from the caller and the response goes back to that caller.

Email and Email Response show captured email and reply information. A recorded reply body is not by itself evidence that a recipient received a message.

Use the performance view for the selected Action to identify callout latency, query cost, DML work and limit consumption where measurements were recorded. Keep transaction totals separate from individual Action measurements.

CSV Action performance aggregates measured chunks, while the general parent Job metrics describe the latest transaction. Queue waiting is not Action execution duration. See Review CSV import results.

Jobs created before Action snapshots were saved can show a reconstructed timeline labelled Recorded. That view uses saved Job data and the available configuration; it does not supply missing original per-Action timings, statuses or order.

Use it to inspect the data that exists. Do not compare reconstructed entries as though they were measured Action executions.

Replay Job starts new work using the supported replay path and current configuration. Review prefilled values and possible external or Salesforce effects before running it. A previous failure does not prove that nothing committed.

CSV Replay is disabled. Prepare a controlled correction run from the source-row outcomes instead. Email replay reprocesses captured content and does not replace testing real delivery.

For an escalation, include the Job link, Payload, first failed Action, error, relevant request or response details and any necessary metrics. See Troubleshoot failed Jobs.