[Silthus]

Problem

• Workflow authors who test an email step with an empty recipient see a green "Success" banner, though nothing was sent.
• #127189 added a yellow skip banner, but the worker never reports this skip.

Note

🔵 Merge risk: low · two-way door (merge-risk rubric)

• Sending, metrics and billing ignore the new field. The worst case is a wrong test banner.
• Revert: git revert the merge commit.

Changes

• A test send to an empty recipient now shows the yellow "Skipping send" banner.
• The worker's missing-recipient skip now returns emailSendResult, like the other skip branches.

Before	After

How did you test this code?

Local stack at ee1f371, invented data:

• The test endpoint returns the skip result (raw below). Master returns none.
• A filled recipient still delivers.
• A real empty-recipient run matches master.
• Not checked: production.

Test rationale: the empty-recipient it.each now asserts emailSendResult, which fails on master.

Raw test endpoint response at ee1f371 (trimmed)

POST /api/projects/1/hog_flows/<id>/invocations/   person without billing_email
{"nextActionId":"exit_node","status":"success","errors":[], ...,
 "emailSendResult":{"status":"skipped","reason":"Skipping send: the recipient has no email address. Add a filter so only people with an email address reach this step."}}

Same request on master: no emailSendResult key.

POST /api/projects/1/hog_flows/<id>/run/   real run, no person
app_metrics2: email_missing_recipient 1, email_queued 1, succeeded 3   (same on master)
hog_invocation_results: succeeded                                      (same on master)

Release status

• No feature flag controls this change

Docs update

• None.

🤖 Agent context

Autonomy: Human-driven (agent-assisted)

Agent: Claude Code, Claude Opus 5.5

Skills: /writing-tests, /writing-pr-descriptions

More context for AI agents

• Session: T3 Code lane for fix(workflows): report a skipped test email as skipped #127189; tools: fleet proof, Playwright on a local preview, cross-model review panel.
• Decisions: split from fix(workflows): report a skipped test email as skipped #127189 so CDP delivery code gets teammate review and fix(workflows): report a skipped test email as skipped #127189 stays frontend only.
• Decisions: review panel nit for a shared skip helper declined here; it rewrites three untouched branches and changes skipped semantics.
• Follow-ups: one skip helper for all executeSendEmail skip branches, with a stated rule for when skipped is set.
• No duplicate: feat(workflows): report blocked and failed workflow sends #127135 changes the same branch to report analytics, but does not set emailSendResult. Expect a small textual conflict.
• Public artifact: all test data is invented.

🤖 Generated with Claude Code

[trunk-io]

😎 Merged successfully - details.

[github-actions]

🤖 CI report

✅ Trunk lane — non-backend lane

This PR is assigned to the non-backend lane. It does not run backend Python tests and may merge in parallel with PRs in other lanes.

✅ Duplication (Python) — clean

New Python code duplication introduced by this branch. Fails at 70+ tokens in app code, or 150+ tokens when both copies live in test files. Advisory while the gate proves itself: extract a shared helper instead of copying.

✅ Duplication (TypeScript) — clean

New TypeScript code duplication introduced by this branch. Fails at 70+ tokens in app code, or 150+ tokens when both copies live in test files. Advisory while the gate proves itself: extract a shared helper instead of copying.

[hosthog]

HostHog preview — posthog-desktop-web

The previews for this PR have been torn down and no longer serve.

[parameterai]

Risk: No findings

The PR makes the worker's missing-recipient skip path in EmailService report an emailSendResult (status skipped) so the test-send UI shows the yellow skip banner, matching the suspension, workflow-pause, and suppression skip branches. The reason string is a fixed constant, the existing skipped flag and metrics are untouched, and the value only flows to the invoking team's own API response — no security risk introduced.

_{Sentinel reviewed ee1f371 · Review settings}

[stamphog]

Approved.

The response change enters API territory, with assurance supplied by owning-team authorship and a targeted test assertion. No unresolved review concerns or other refusal grounds were found.

Gate mechanics and policy version

Gate		Result
prerequisites	✓	all clear
deny-list	✓	no deny categories matched
size	✓	6L, 1F substantive, 10L/2F incl. docs/generated/snapshots — within ceiling
tier	✓	T1-agent / T1a-trivial (10L, 2F, single-area, fix)
stamphog 2.7.0		.stamphog/policy.yml @ ee1f371 · reviewed head ee1f371

[Silthus]

/trunk merge

[deployment-status-posthog]

Deploy status

Environment	Status	Deployed At	Workflow
dev	✅ Deployed	2026-11-04 08:54 UTC	Run
prod-us	✅ Deployed	2026-11-04 09:09 UTC	Run
prod-eu	✅ Deployed	2026-11-04 09:09 UTC	Run