Auto-Retry for Soft Errors
When Council encounters temporary issues (like network glitches), it automatically retries to provide a seamless experience.
How it works
- First retry: Waits 1 second, then tries again
- Second retry: Waits 2 seconds, then tries again
- Third retry: Waits 4 seconds, then tries again
- If all retries fail, you'll see an error screen with options
You'll see a toast notification
"Connection issue. Retrying... (attempt 2)"
Which errors auto-retry?
These errors trigger automatic retry:
- DOOR-001: Network connection failed
- DOOR-004: Key verification failed
- DOOR-009: Operation timed out
- AUTH-004: Connection timeout
- MSG-001: Message send failed
- ATT-001: Download failed
- ATT-005: Upload failed
Which errors don't auto-retry?
These errors require user action:
- DOOR-003: Wrong encryption key (you need to re-enter)
- DOOR-005: Session expired (you need to sign in)
- All other errors (require user action)
Exponential backoff
The increasing wait times between retries (1s, 2s, 4s) help avoid overwhelming the server during temporary issues while still resolving problems quickly.