Skip to content

feat(relayer): add max message backoff seconds config#379

Closed
danwt wants to merge 1 commit intomain-dymfrom
danwt/claude-cap-message-backoff
Closed

feat(relayer): add max message backoff seconds config#379
danwt wants to merge 1 commit intomain-dymfrom
danwt/claude-cap-message-backoff

Conversation

@danwt
Copy link
Copy Markdown

@danwt danwt commented Dec 5, 2025

Add optional config parameter to cap message backoff time

🤖 Generated with Claude Code

Add a new optional configuration parameter `maxMessageBackoffSeconds`
to cap the maximum backoff time for message retries.

Changes:
- Add `max_message_backoff_seconds` field to RelayerSettings
- Parse config value from `maxMessageBackoffSeconds` in settings parser
- Add field to MessageContext to pass cap through to backoff calculation
- Modify `calculate_msg_backoff()` to accept and apply optional cap
- Update all call sites including tests to pass the cap parameter
- If unset, the existing behavior is maintained (no cap applied)

This allows operators to limit the maximum retry backoff time, which is
useful for controlling message processing latency in high-throughput
environments.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@danwt danwt changed the base branch from main to main-dym December 5, 2025 10:32
@danwt
Copy link
Copy Markdown
Author

danwt commented Dec 5, 2025

Superseded by #380 which uses a simpler hardcoded approach

@danwt danwt closed this Dec 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant