Skip to main content

Workflow Processed-Event Storage

Summary​

ProcessedIntegrationEvent is mapped as an idempotency ledger for future consumed integration events.

Mapping​

The record stores application GUID, unique event identifier, required event type/outcome, optional numeric tenant/correlation and source-service text, plus processed time.

Constraint and isolation​

Event identifier is unique. No tenant global query filter applies.

Runtime status​

No Workflow message consumer registration or write path for processed-event rows was found. Storage is therefore Foundation rather than active processing evidence.

Limitations​

No relationship to outbox records, cleanup, outcome taxonomy constraint or consumer-specific partition exists.

Requires Confirmation​

Consumer roadmap, tenant isolation, retention and retry/idempotency semantics require confirmation.

Source References​

  • microservices/src/workflow-service/Infrastructure/WorkflowDbContext.cs
  • microservices/src/workflow-service/Infrastructure/Migrations/20260706165438_InitialWorkflowSchema.cs
  • microservices/src/workflow-service/Program.cs

See Also​

Keywords​

Workflow database, EF Core, Workflow schema.

Revision Information​

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