Problem Statement:

Harness has an established troubleshooting surface for inward signals (Trigger Execution Troubleshooting) where users can inspect payloads and resolution logic. However, an equivalent surface does not exist for outbound signals (Slack, Email, MS Teams, Datadog, and Git PR Status updates).

Because these are currently handled as asynchronous, best-effort tasks, they fail "out-of-band." This creates a scenario where a pipeline execution is marked Green in the Harness UI, but the external state is broken (e.g., a PR status check remains "Pending" indefinitely or a critical production alert is never delivered).

The "False Positive" Connection Test:

Connector "Test Connection" functionality typically validates network reachability or basic read access. It does not verify the specific write-level scopes or functional permissions (e.g., write:statuses for GitHub or specific channel permissions for Slack) required at runtime. A connector can return a "Success" state while being functionally incapable of completing the pipeline task.

Visibility Gap & Failure Modes:

Without runtime logs in the UI, users cannot self-diagnose common integration failures:

Expired/Rotated Tokens: Credentials that have become invalid since the last connection test.

Provider Rate Limiting: Throttling from external APIs (e.g., GitHub's 5000/hr limit) that causes updates to be dropped.

Missing Scopes: Tokens that lack the specific permission to update a status or post to a sink.

JEXL Resolution Errors: Payloads that become malformed during variable resolution (e.g., a null variable producing invalid JSON).

Proposed Solution:

Implement an "Outbound Delivery" or "External Signals" tab within the Pipeline Execution UI that provides:

Request Audit: The final resolved payload sent to the external service.

Provider Response: The raw HTTP status and response body (e.g., 403 Forbidden: insufficient_scope or 429 Too Many Requests).

Traceability: Direct correlation between the planExecutionId and the specific delivery task.

Value:

MTTR Reduction: Enables customers to diagnose integration issues without requiring Harness Support intervening, being bottleneck

Feedback Reliability: Ensures the Harness execution status accurately reflects the state of the broader CI/CD ecosystem.