LMS Outbox and Delivery Diagnostics

Summary

Source-backed Draft reference for LMS Outbox and Delivery Diagnostics across the implemented Training Service and, where applicable, Gateway surface.

Audience

API consumers, engineering, QA, support, architecture, security, product, and implementation reviewers.

Reference Content

Confirmed API

One native collection route returns tenant-filtered outbox records ordered newest first with the same bounded take behavior as audit/timeline. It exposes staged message evidence but does not implement retry, replay, cancellation, dead-letter, failure filtering, or delivery-state mutation.

The endpoint does not prove broker delivery or downstream processing. Training source stages eight invoked event families, but no Training-hosted relay trigger or inbound consumer was found in runtime registration.

Diagnostic question	API evidence
Staged event count/list	Implemented through collection response
Delivered/failed/retried status	No dedicated projection or route
Retry operation	Not implemented
Processed inbound evidence	Persistence set exists; no mapped API
Authorization	No endpoint policy found

Because outbox records may contain internal metadata and business context, direct entity exposure without a declared authorization/redaction policy is a public-exposure risk requiring confirmation. Payload examples and infrastructure details are intentionally excluded.

Source References

• microservices/src/training-service/Api/TrainingEndpoints.cs
• microservices/src/training-service/Program.cs
• microservices/src/training-service/Infrastructure/Persistence.cs
• microservices/src/training-service/Infrastructure/TrainingDbContext.cs

Related Articles

• LMS API documentation
• LMS technical documentation

See Also

• Endpoint catalog
• API limitations

Keywords

• LMS API
• Training Service
• Source-backed contract

Revision Information

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