Watch messages flow through NimBus.
Simulated CRM, ERP, and storefront traffic on a NimBus topology. Inject a payment failure to watch a session block, defer later messages, and recover.
Topology mirrors real NimBus conventions: one Service Bus topic per endpoint (topic name = endpoint id),
event-type forward subscriptions route copies to each subscriber's endpoint topic, and
[SessionKey]-ordered sessions block on failure — successors park on the endpoint's
Deferred subscription. Every handler outcome flows through the central Resolver topic into
the message store, SQL Server or Cosmos DB (ResolutionStatus: Pending · Deferred · Failed · DeadLettered · Completed · Skipped), where the
WebApp acts on blocked sessions by sending recovery commands to the Manager topic, for an operator
or for the Ops Triage AI agent, which works through the WebApp's operator MCP endpoint.
The AI agents are illustrative. Real agents can join the bus through the REST agent API.