Notification delivery · Verify

Notification Failure & Idempotency Check

Verify one notification delivery invariant through bounded success, failure, duplicate, retry, consent, and provider-status scenarios.

Vibe Coding 1.3.0 · vibe-notifications · English technical instructions

← Back to search

Use this workflow

Use this workflow in Codex or Claude Code with the free Vibe Coding plugin. Choose your assistant and prompt language, then add your task details after the prompt.

Prompt

Use $vibe-notifications, workflow “Notification Failure & Idempotency Check” (ID: notification-failure-idempotency-check). Follow this workflow for the task below. Report the result in English.

Install the plugin

Operation

Verify the selected invariant through bounded scenarios in an authorized environment. Do not turn verification into unrelated implementation. Return passed, failed or blocked, with actual evidence and any missing required scenario.

Goal

Verify one notification delivery invariant through bounded success, failure, duplicate, retry, consent, and provider-status scenarios.

Required input

Provide notification type/channel, selected invariant, expected delivery/status behavior, implementation summary or patch boundary, safe sandbox/mock environment, fixtures, and repository-native commands.

Scenarios

Trigger the notification once and verify the rendered payload/status.
Trigger duplicates or job redelivery and prove no duplicate side effect unless explicitly allowed.
Exercise provider failure, timeout/rate limit, retry, bounce/suppression/status webhook, and recovery behavior.
Verify consent/unsubscribe, locale/template data, and sensitive metadata handling where relevant.

Workflow ID: notification-failure-idempotency-check · View the versioned source · Shared workflow and authority rules