Skip to main content

Asset Management Troubleshooting

Summary​

Complete Draft troubleshooting documentation for Asset Management. Every page follows a non-destructive pattern — symptoms, likely causes, safe diagnostics, safe resolution, validation, evidence to collect, and an escalation boundary — and never includes destructive commands.

Audience​

Support and operations engineers, backend engineers, QA, security reviewers, and product owners.

Overview​

Troubleshooting is organized by failure surface: authentication and tenant context, the asset create/update path, duplicate asset codes, list and detail reads, the assignment and return lifecycle, requests and approvals, workflow callbacks, damage/loss/retirement/deletion, documents, notifications, the outbox, the gateway and compatibility slice, audit and timeline, and migrations and backfill. A general diagnostic decision tree routes a reader from a symptom to the right page.

All diagnostics are read-only and observational. Pages never instruct a reader to run SQL, edit the outbox, replay events, issue broker commands, run migrations or backfill, or inspect credentials. Escalation boundaries name the owning team for each surface, defaulting to Requires confirmation where ownership is not established in source.

Documentation map​

Requires confirmation​

Support escalation ownership, monitoring/alert routing, and production diagnostic access require confirmation.

Source References​

  • microservices/src/asset-service/Api/EndpointResults.cs
  • microservices/src/asset-service/Application/Commands/AssetCommands.cs
  • microservices/src/asset-service/Api/AssetEndpoints.cs
  • microservices/scripts/smoke-asset.ps1

See Also​

Keywords​

  • Asset troubleshooting
  • Safe diagnostics
  • Escalation

Revision Information​

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