Use the Home tab when you need a fast view of Payloads health across the org.

Home is not where you configure the integration details. It is where you see whether Payloads is running cleanly, whether Jobs are failing, whether runtime is changing, and whether cleanup, batch, or subscription items need attention.

Think of Home as the operational starting point. It will not tell you every detail of a failed run, but it should help you decide where to look first.

Home combines recent Payloads activity with org-wide usage and queue information.

The summary cards show the current state of the org.

Jobs Last 24h shows recent Job volume, completion percentage and failed Jobs. Average Duration Last 30d shows average runtime and the 95th percentile across that window. Cleanup Service shows whether the Job cleanup service is running and when it should run next. Subscription shows the current plan state and whether any billing action is required.

These cards are intentionally high level. Use them to spot whether something needs attention, then open the relevant tab or Job for the detailed evidence.

Org usage shows Daily API Requests, Async Apex Executions, Platform Events Published and Delivered, Data Storage and File Storage. Read each card's time window: event publishing uses the last hour, API usage and event delivery use the last 24 hours, and storage shows current usage.

Apex queue status shows Batch jobs queued or active, the Batch flex queue, Queueables waiting or running, and the oldest waiting job. These figures cover jobs visible to you across the org. They can include work outside Payloads; they are not the same as the Payloads Batch Engine's ready-job count.

Use these panels to distinguish an org capacity problem from a failure in a particular Payload. Check the affected Job before retrying work.

Use Job Activity Last 30d to see whether volume or failures have changed recently.

A single failed Job may be a data issue. A sudden spike in failures usually means something changed: the external system, Credential, Endpoint, mapping, Salesforce data, or a permission path.

Open the Jobs tab or the relevant Integration when you need to inspect specific runs. Home is the signal; the Job record is where you confirm the cause.

For Job details, see Understand Job records.

Use the duration panels to spot slow Payloads.

Slow runtime can be caused by a slow external API, large query results, complex mappings, many Data Target records, or Salesforce limits pressure.

If a Payload is getting slower, open recent Jobs and compare callout duration, query duration, DML duration, CPU time, heap, query count, and DML row count. That comparison usually tells you whether the bottleneck is outside Salesforce, inside the query and mapping work, or in target record writes.

The integration health table groups activity by Integration.

Use it to find which Integration has recent activity, high failure rates, or slower average duration.

This is often the fastest route from "Payloads has a problem" to the specific Integration that needs review. Once you know the Integration, open its Jobs and Payloads rather than searching across the whole app.

Needs Attention highlights operational items that should be reviewed.

Examples include recent failures, cleanup not running, subscription issues, high API usage, or slower Payloads.

Treat attention items as a triage list. They tell you where to look first, not necessarily what the final fix is. Clear the underlying issue, then refresh Home to confirm the operational state has changed.

The cleanup status shows whether the cleanup scheduler is running.

Payloads can delete old Jobs based on each Payload's retention settings. When cleanup is stopped, old Jobs can build up and storage usage can grow. If Home shows cleanup attention items, review both the service status and the individual Payload retention settings.

For setup steps, see Configure Job retention and cleanup.

When reviewing Home, check:

If Home shows an issue, open the relevant Job before changing configuration.

Open the affected Job from the operational view, then select the failed Action in its timeline. Review that Action’s inputs, output and error before changing configuration. The Home totals do not replace per-Action evidence.

For CSV imports, open the Job’s progress and result summary. Completed means the import finished processing; row failures can still be present. Dedicated CSV Batchable work should be investigated through its Job and async execution, rather than assuming it uses the general Batch Engine.