Workflow Event Correlation

Audience

Developers, QA, support, architects and integration reviewers.

Summary

Each mapped integration event receives a new event identifier. Its correlation identifier is the workflow-instance identifier rendered as text; the originating domain-event identifier is not propagated.

Reference Content

Field	Workflow mapping
Event identifier	Newly generated integration-event identifier
Correlation identifier	Workflow-instance identifier
Causation identifier	Not populated
Envelope tenant identifier	Not populated
Envelope user identifier	Not populated
Payload tenant reference	Numeric tenant reference is retained
Occurrence time	Copied from the domain event
Source and schema	Workflow source; schema version 1

The outbox processor exposes selected envelope data as transport metadata. Request correlation is not propagated by the verified Workflow mapping.

Requires Confirmation

Distributed trace propagation, causation rules, actor identity and the intended relationship between envelope tenancy and payload tenancy require confirmation.

Source References

• microservices/src/contracts/Events/IntegrationEvent.cs
• microservices/src/shared-kernel/Messaging/OutboxProcessor.cs
• microservices/src/workflow-service/Infrastructure/WorkflowDbContext.cs
• microservices/src/workflow-service/Messaging/WorkflowIntegrationEvents.cs

Related Articles

• Message contracts
• Idempotency
• Event source map

See Also

• Technical documentation

Keywords

Workflow events, correlation, causation, tenancy.

Revision Information

• Status: Draft
• Last reviewed: 2026-07-20
• Next review: 2026-10-20