Summary
A single WhatsApp message flows through webhook → command parser → router → stellar/soroban services → back out as a reply; debugging a failed send currently means grepping logs with no shared identifier tying the steps together.
Description
Generate a correlation ID per inbound webhook message and thread it through the router, Stellar/Soroban service calls, and outbound reply, including it in every structured log line for that request (building on the pino logging setup).
Include the correlation ID (or a short reference) in error replies sent back to the user, so a user reporting 'my send failed' can be looked up quickly.
Add a test asserting the same correlation ID appears across log lines for a single simulated message handling.
Deliverables
- Correlation ID generated and threaded through the pipeline
- Included in logs and in user-facing error replies
- Test asserting consistent propagation
Dependencies
None
Summary
A single WhatsApp message flows through webhook → command parser → router → stellar/soroban services → back out as a reply; debugging a failed send currently means grepping logs with no shared identifier tying the steps together.
Description
Generate a correlation ID per inbound webhook message and thread it through the router, Stellar/Soroban service calls, and outbound reply, including it in every structured log line for that request (building on the pino logging setup).
Include the correlation ID (or a short reference) in error replies sent back to the user, so a user reporting 'my send failed' can be looked up quickly.
Add a test asserting the same correlation ID appears across log lines for a single simulated message handling.
Deliverables
Dependencies
None