Skip to main content

Asset Diagnostic Decision Tree

Summary​

This page routes a reported asset symptom to the troubleshooting page most likely to resolve it. It applies the non-destructive method: confirm tenant context first, then determine which backend served the request, then narrow to the specific behavior. Use the diagram to reach a starting page quickly, then follow that page's read-only diagnostics.

Audience​

Support engineers triaging incoming tickets, and developers or QA engineers who need a fast route from a symptom to the right investigation page.

Reference Content​

Start at the top with the observed symptom and follow the branch to a target page.

Routing notes​

  • Always confirm tenant context before concluding data is missing, since reads are tenant-filtered.
  • Read the X-Gateway-Route-Source header early when behavior or response shape is unexpected.
  • A 409 on a direct approve or reject usually means the asset is workflow-managed.
  • A pending outbox backlog usually means the broker is unavailable.
  • A missing email at emit is expected until RecipientEmail enrichment.

Source References​

  • microservices/src/asset-service/Api/AssetEndpoints.cs
  • microservices/src/asset-service/Api/AssetCompatEndpoints.cs
  • microservices/src/gateway-api/Program.cs
  • microservices/scripts/smoke-asset.ps1

See Also​

Keywords​

decision tree, symptom routing, triage, tenant context, route source

Revision Information​

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