Use Run Payload to supply test inputs and inspect the resulting Job while building an integration. Choose an entry point that exercises the behaviour you intend to deploy.

Check the request endpoint, method, credentials, content types and response policy. Review the Action sequence, Query limits, required Dynamic Inputs and any Target or Flow that changes Salesforce data.

Use controlled records and a test destination. A manual run performs the configured work; it is not a preview or an automatic rollback.

Select Run Payload in the Payload header. In the Actions workspace this is the send icon; hover to confirm its label.

The runner shows fields appropriate to the type. Outbound and Credential runs expose callout context and Dynamic Inputs. Inbound runs can accept an Endpoint and request data. CSV Import provides upload or existing-file selection and its dedicated asynchronous modes.

Email Handler's manual Run Payload control is disabled. Test the actual Email Service with a controlled message, or use the supported replay of captured email when checking processing.

Enter the Dynamic Input values declared by the mappings. For Inbound simulation, supply the request content, headers and parameters needed by the configured contract. Also test the actual Endpoint before relying on the simulated run for production behaviour.

Choose the available Firing Mode where the runner offers it. Do not assume every manual run is Immediate. Inbound follows its creation-time mode; CSV supports Queueable or Batchable.

For manual Outbound Batchable execution, Actions with Targets or Flows are restricted to one Job per execution scope. Other entry points can reject that combination entirely. See Understand Action order and execution limits.

Select Run Payload when the inputs and effects are understood.

Open the created Job and follow the Action timeline. Check captured inputs, Query results, generated HTTP content, response status and Target or Flow outcomes.

For asynchronous work, an accepted or queued Job is not a completed result. Wait for its terminal state and inspect any row-level outcomes before declaring the test successful.

For CSV-specific controls and source cleanup, see Run a CSV import.

Replay Job uses the supported runner or replay path with saved values and current configuration. Review those values and any effects already produced by the earlier run before executing again.

CSV Replay is disabled. Email replay reprocesses saved content and is not a full email-delivery test.

See Understand Job records and Troubleshoot failed Jobs.