Scheduled Messages
The Scheduled Messages view shows all messages queued for future delivery in your Wolverine services. These are messages scheduled with bus.ScheduleAsync(message, deliveryTime) or similar APIs that are waiting in the durable outbox.
Scheduled Messages Grid
Each row shows:
| Column | Description |
|---|---|
| Message Type | The .NET type name of the scheduled message |
| Service | Which service owns this scheduled message |
| Tenant | Tenant ID for multi-tenant services |
| Scheduled At | When this message was originally scheduled |
| Execute At | When the message is due to be delivered |
| Overdue | Whether the execute time has passed without delivery |
| Message ID | The Wolverine envelope GUID |
Messages that are overdue (past their execute time but not yet delivered) are highlighted in red.
Filtering
Filter the grid by:
- Service — scope to a specific service
- Tenant — scope to a specific tenant
- Message Type — filter by type name
- Status — All, Upcoming, Overdue
- Time Range — filter by scheduled-at or execute-at time
Message Detail
Click a row to open the detail panel showing:
- Full message body — formatted JSON
- Envelope headers — correlation ID, source address, original destination
- Execution schedule — scheduled at, execute at, current time, time remaining/overdue
Edit
Opens a form with two editable fields:
- Execute At — reschedule the delivery time. The new time must be in the future.
- Message body — modify the JSON payload. Useful when the message data needs correction before it fires.
After editing, click Save to send the EditScheduledMessage command to the owning service.
Cancel
Permanently removes the scheduled message from the durable outbox. This is irreversible. The message will never be delivered. Requires confirmation.
Overdue Messages
A scheduled message is overdue when its execute time has passed but it has not been delivered. Common causes:
- The service was not running when the message was due
- The service's durable outbox listener was paused
- A database connectivity issue prevented the scheduler from running
Overdue messages will typically be delivered as soon as the service resumes normal operation. They appear in the Overdue filter for monitoring during incidents.
Multi-Tenant Scheduled Messages
For multi-tenant services, scheduled messages are stored in the tenant-specific outbox database. The Tenant filter scopes queries to a specific tenant's data, and edit/cancel operations target that tenant's database.