🌪️ Chaos - Idempotent Retry Logic Test

Testing whether the same streamId produces consistent final state regardless of failures/retries. Mirrors production Sessions.streamMessage() + BaseAgent.transmitStreamWithRetry behavior.

WebSocket: ❌ Disconnected

Test Scenarios

Happy Path
30s, no failures
Single Retry
Fail at part 50, retry once
Production (2min)
2min stream, deploy to test

Live Feed

Waiting for events...

Event Log

No events yet...

Testing Instructions

  1. Happy Path: Click "Happy Path" to test successful completion
  2. Single Retry: Click "Single Retry" to test recovery from simulated failure
  3. Deployment Test: Click "Production (2min)", wait 30s, then run npm run deploy
  4. Idempotency: Run the same scenario twice with same streamId - should return immediately
  5. Inspect: Click "Inspect" to see full stream state including content preview
  6. State Comparison: Click "Check State Comparison" to detect stuck state (in-memory vs SQL)
Key Invariant: For any streamId, regardless of failures/retries, the final state should be:
  • Status = "complete"
  • Parts received = Total parts
  • Content = concatenation of all parts in order