Actions

The Actions tab is the control center for managing a repository’s automated triggers. It is only visible to admins and above.

Subscriptions

Subscriptions are displayed as cards in a grid. Each card shows:

• Name and kind badge — webhook subscriptions show a blue badge; older cron subscriptions that still appear in the UI render a muted badge
• Status indicator — a green dot with “active” label, or a gray dot with “paused” label
• Last run status — the most recent execution result

Click any card to open the subscription detail view.

Subscription Detail

The detail view shows quick stats (last run, total runs in the past 7 days, success rate) and provides:

• Pause / Resume controls — webhook subscriptions show Pause or Resume depending on current state. Older cron subscriptions are read-only in the detail view; a Pause control appears only while the entry is still active, and paused cron entries cannot be resumed from this screen.

Run History

Below the quick stats, a paginated list of recent runs shows:

• Status badge — the run’s current state. You’ll see one of these labels:
  • pending — queued and waiting to start
  • running — currently executing
  • processing — accepted by the handler and continuing asynchronously while WarmHub waits for a callback
  • retry wait — failed but scheduled for automatic retry
  • succeeded — completed successfully
  • suppressed — delivery was skipped because the subscription no longer had authority to deliver
  • failed terminal — non-retryable terminal failure; requires investigation
  • dead letter — retries exhausted without success; will not retry automatically
• Run ID
• Attempt count (e.g., “1/3 attempts”)
• Error codes and messages (if any)

The list loads 50 runs at a time. Click Load more at the bottom to fetch the next page of results.

Expand any run to see individual attempt details — timing, HTTP status, and response snippets.

Configuration

Below Run History, a collapsible Configuration section shows:

• Webhook URL — for webhook subscriptions, the origin of the registered endpoint is shown in redacted form (e.g., <origin>/***). The full URL is not displayed after initial creation; to inspect the raw URL or update it, see Managing Subscriptions.
• Shape Filter — the bound shape name this subscription matches on, when one is set. Subscriptions that watch a shape’s own lifecycle (its adds, revises, and retracts) may show no shape here. The full filter expression is not displayed in this card. See Subscription Filter JSON for filter syntax.
• Component — for subscriptions owned by a component, the component’s public Org/Name ref is shown here.

Bound Credentials

A separate section below Configuration lists the credential sets bound to the subscription. A bound credential set holds the authentication headers and signing secrets WarmHub attaches to outgoing webhook deliveries — bearer tokens, API keys, or an HMAC signing secret — so the receiving endpoint can authenticate and verify them. See Subscription Credentials & Signatures for more on credential binding.

Credentials

The Actions tab also provides credential management:

• Create credential sets with a name, scope (repo or organization), and optional description
• View existing credential sets with their key names, scope, and status
• Bind a credential set to a subscription for authenticated webhook delivery
• Revoke a credential set permanently (with an optional reason)

CLI Equivalents

• wh sub list — list subscriptions
• wh sub view <name> — subscription details
• wh sub log <name> — run history
• wh credential list — list credential sets

See the CLI reference and subscriptions documentation for more details.