Helpdesk Transactions and Save Boundaries

Audience

Developers, database engineers, QA, support and architects.

Summary

No explicit transaction API is used in reviewed Helpdesk handlers. Each SaveChanges call relies on EF Core's normal single-save transaction behavior.

Reference Content

Lifecycle handlers generally save domain, audit, timeline and outbox rows together. Outbox status changes use separate saves. Attachment upload occurs before persistence; attachment local deletion does not remove the external file. SLA check accumulates a batch then saves once.

Requires confirmation

Explicit transaction/isolation policy, retry behavior, partial-failure compensation, maximum batch size and distributed consistency require confirmation.

Source References

• microservices/src/helpdesk-service/Api/HelpdeskEndpoints.cs
• microservices/src/helpdesk-service/Infrastructure/Persistence.cs
• microservices/src/helpdesk-service/Infrastructure/DocumentServiceClient.cs
• microservices/src/helpdesk-service/Backfill/HelpdeskBackfill.cs
• microservices/src/helpdesk-service/Infrastructure/DevelopmentSeeder.cs

Related Articles

• Database overview
• Schema reference
• Database limitations

See Also

• API documentation
• Technical documentation

Keywords

SaveChanges, transaction boundary, outbox atomicity, external consistency.

Revision Information

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