debugging-reactive-chains

What problem does it solve?

Debugging reactive chains in Firefly Framework services can be difficult because exceptions occur on different threads from the assembly of the chain, and reactive stack traces are often unclear.

Core Features & Use Cases

• Reactor debugging fundamentals: using log(), checkpoint(), Hooks.onOperatorDebug, and ReactorDebugAgent to illuminate signal flow and stack traces.
• Diagnosing common reactive issues: empty signal, timeouts, backpressure, context loss across schedulers, and hidden errors in saga or command pipelines.
• Practical guidance and examples for tracing errors across CommandBus, QueryBus, EDA, and saga orchestration.

Quick Start

Enable Reactor debugging at startup (e.g., Hooks.onOperatorDebug or ReactorDebugAgent) and review logs and checkpoints to identify the failing operator in the reactive chain.