Helpdesk Event Limitations
Events
- Not implemented: no Helpdesk domain-event layer.
- Partial: ten lifecycle names share one broad snapshot contract rather than event-specific contracts.
- No attachment-removed, general ticket-updated, category, priority or configuration events were found.
Integration
- Not implemented: no Helpdesk hosted relay or verified processor invocation.
- Document Service and Gateway are synchronous boundaries, not event consumers.
- No external Helpdesk consumers were found.
Delivery
- Current automatic Helpdesk-to-broker delivery is Not implemented.
- No publisher confirmations, terminal dead-letter status, cleanup, retention, claim/lock, attempt ceiling or backoff exists in the verified Helpdesk path.
Ordering
- Only a global
OccurredAtUtcquery order exists. - There is no per-ticket sequence or durable ordering guarantee.
Correlation
- Contract fields exist, but Helpdesk populates correlation and causation with null.
- Request-to-notification lineage is incomplete.
Notifications
- Notification Service covers all ten names, but delivery depends on relay, recipient data, preferences, templates and channel sender behavior.
- The publisher contains an administrator placeholder address; production suitability Requires confirmation.
Compatibility
- Compatibility create and status patch emit events; general update and backfill do not.
- Generic status changes do not preserve lifecycle-specific event semantics.
Testing
- Dedicated Helpdesk event, relay, replay, duplicate and end-to-end tests were not found.
- Poison-message and recovery exercises are not verified.
Source References
microservices/src/helpdesk-service/Program.csmicroservices/src/helpdesk-service/Api/HelpdeskEndpoints.csmicroservices/src/helpdesk-service/Infrastructure/Persistence.csmicroservices/src/notification-service/Application/NotificationDispatcher.cs
Related Articles
Revision Information
Draft source-backed documentation reviewed on 2026-07-20; next quarterly review is 2026-10-20.