Skip to main content

LMS Outbox Operations

Summary​

Training can stage and inspect outbox records, and the shared processor can update processing state if invoked. No Training relay trigger is registered.

Safe operational evidence​

Review counts and sanitized categories for pending, failed, processed, occurrence time, retry count, and correlation presence through approved read-only diagnostics. Do not inspect payloads in public evidence.

Replay, cleanup, dead-lettering, reconciliation, terminal retry, and processor scheduling are Not implemented or Require confirmation. This page provides no replay or recovery command.

Safety and confirmation boundary​

No production command, secret, configuration value, internal address, infrastructure detail, direct data change, or replay instruction is provided. Production ownership, approvals, service objectives, alerting, and recovery authority require confirmation.

Source References​

  • microservices/src/training-service/Infrastructure/Persistence.cs
  • microservices/src/shared-kernel/Messaging/OutboxProcessor.cs
  • microservices/src/training-service/Program.cs

See Also​

Keywords​

  • LMS operations
  • LMS Outbox Operations

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-17
  • Review cycle: Quarterly