Overview
Use the failed-message workbench, attempt history, conversation context, retry policy, replay requests, provider selection, and channel options to recover delivery.
Prerequisites
Permissions required
Steps (4)
-
1
Open the failed message
Review failure category, provider result, conversation, recipient, and technical state.
Tips
Validation
Success criteria
-
2
Inspect attempts and policy state
Review message attempts, retry attempts, route decisions, provider status, and recipient eligibility.
Tips
Validation
Success criteria
-
3
Choose the recovery action
Retry, bulk retry, request replay, choose another eligible provider/channel, or correct recipient data as appropriate.
Tips
Validation
Success criteria
-
4
Verify final state
Track retry completion and message state history through delivered, failed, or resolved outcome.
Tips
Validation
Success criteria
About this guide
PulseGate is the communications control plane for Velaxe workspaces. Applications send business communication through trusted contracts while PulseGate resolves recipients and templates, applies authorization and policy, routes delivery, records message state, and publishes clean events.
Operations teams get a dedicated Messenger workspace for conversations, contacts, campaigns, approvals, failed messages, and media, plus administration for provider connections, sender identities, routing, templates, consent, suppression, quiet hours, cost rules, audit, and reports.
Durable workers handle dispatch, schedules, reminders, campaigns, provider webhooks, retries, reconciliation, metrics, retention, exports, media processing, and operational recovery. Handler, RCP, Bridge v2, EventBus, and ContextResolver contracts keep workspace integrations governed and source-aware.