Skip to main content

Helpdesk Event Correlation

Verified behavior​

The shared contract supports nullable CorrelationId and CausationId, and the broker publisher can map them to message metadata. Helpdesk applies shared request-correlation middleware, but AddTicketEvent explicitly supplies null for both fields and supplies no event user ID.

Consequently, current Helpdesk lifecycle outbox rows do not connect the HTTP request correlation identifier to integration delivery. Notification Service computes an effective correlation value when consuming an envelope, but that consumer fallback does not restore the original request lineage.

Classification​

  • Contract fields: Implemented.
  • Helpdesk population: Not implemented.
  • Original request-to-notification trace continuity: Not implemented.
  • Required propagation policy: Requires confirmation.

Source References​

  • microservices/src/contracts/Events/IntegrationEvent.cs
  • microservices/src/helpdesk-service/Infrastructure/Persistence.cs
  • microservices/src/helpdesk-service/Program.cs
  • microservices/src/notification-service/Messaging/NotificationEventEnvelope.cs

Revision Information​

Draft source-backed documentation reviewed on 2026-07-20; next quarterly review is 2026-10-20.