feat: implement heartbeat 401 unauthorized back-off logic

[osaas-oscar]

Summary

This PR implements a heartbeat polling back-off mechanism to handle consecutive 401 unauthorized errors, as requested in issue #534.

Changes Made

• Enhanced useHeartbeat hook (src/components/production-line/use-heartbeat.ts):
  • Track consecutive 401 unauthorized errors during heartbeat polling
  • Stop polling after 10 consecutive 401 errors to prevent server spam
  • Automatically resume polling when sessionId changes (after reauthentication)
  • Add detailed logging for 401 errors and back-off state transitions
  • Reset 401 counter on successful heartbeats or non-401 errors
  • Provide manual resume function for advanced use cases

Implementation Details

• Error Detection: Checks for "Response Code: 401" in error messages
• Configurable Threshold: MAX_CONSECUTIVE_401_ERRORS = 10 (easily adjustable)
• State Management: Uses React refs to persist state across re-renders
• Automatic Recovery: Polling resumes when sessionId changes (typical after reauthentication)
• Enhanced Logging: Clear error messages showing progress (e.g., "Heartbeat 401 error (3/10)")

Test Plan

• Verify heartbeat continues normally under good conditions
• Simulate 401 errors and confirm polling stops after 10 consecutive failures
• Test that polling resumes after sessionId changes
• Verify non-401 errors don't trigger back-off behavior
• Check logging output for clarity and usefulness

Behavior

• ✅ Heartbeat polling continues every 10 seconds as before
• ✅ 401 errors are logged with current count (e.g., "Heartbeat 401 error (3/10)")
• ✅ After 10 consecutive 401 errors, polling stops with clear message
• ✅ Polling automatically resumes when sessionId changes
• ✅ Non-401 errors reset the 401 counter and continue polling
• ✅ Successful heartbeats reset the 401 counter

Fixes #534

🤖 Generated with Claude Code

[osaas-oscar]

🔄 Expanded Scope - Added Comprehensive 401 Back-off Protection

I've extended this PR to implement 401 back-off logic across all polling mechanisms in the application:

Additional Files Modified:

1. src/components/production-line/use-line-polling.ts - Production line polling (every 1s)
2. src/components/landing-page/use-fetch-production-list.ts - Production list polling (every 10s)

Complete Coverage:

• ✅ Heartbeat polling (every 10s) - ✅ Already implemented
• ✅ Production line polling (every 1s) - 🆕 Now implemented
• ✅ Production list polling (every 10s) - 🆕 Now implemented

Consistent Behavior Across All Polling:

• Track consecutive 401 unauthorized errors separately from other errors
• Stop polling after 10 consecutive 401 errors with clear logging
• Automatically resume when polling conditions reset
• Enhanced error logging: "[Type] polling 401 error (3/10): [error message]"

This provides comprehensive protection against 401 spam across the entire application, not just heartbeat polling.

Updated Test Plan:

• Test heartbeat 401 back-off (sessionId-based recovery)
• Test production line 401 back-off (joinProductionOptions change recovery)
• Test production list 401 back-off (reloadProductionList/doInitialLoad recovery)
• Verify all polling mechanisms log 401 errors consistently
• Confirm non-401 errors don't trigger back-off in any polling mechanism

🤖 Generated with Claude Code