Skip to content

Adjust reaction timing intervals for Telegram and WhatsApp#328

Merged
milosmns merged 2 commits intomainfrom
claude/fix-notifier-timing-LfK2W
Mar 12, 2026
Merged

Adjust reaction timing intervals for Telegram and WhatsApp#328
milosmns merged 2 commits intomainfrom
claude/fix-notifier-timing-LfK2W

Conversation

@milosmns
Copy link
Contributor

Summary

Updates the reaction notification timing intervals for Telegram and WhatsApp platforms to better align with platform-specific requirements and user experience expectations.

Changes:

  • Telegram: Increased initial delay from 10s to 15s and interval from 10s to 30s
  • WhatsApp: Increased interval from 7s to 15s (initial delay remains 0s)

These adjustments reduce notification frequency and provide better spacing between reaction updates, improving the user experience on these platforms.

Resolves #000 (Please update with actual issue number)

Change types

  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Breaking change (fix or feature that would cause existing functionality not to work as before)
  • Refactoring (improvements to the codebase that aren't necessarily bringing new functionality)
  • Docs update (this change includes or requires a documentation update)
  • CI/CD (automation pipeline changes)

Testing

The existing unit test test_fires_after_initial_delay has been updated to reflect the new Telegram timing values (15s initial, 30s interval). The test now includes an additional cycle to verify the reaction fires at the correct time with the new intervals.

Test Suite

  • test_fires_immediately_when_initial_delay_zero - Updated to reflect new WhatsApp interval (15s)
  • test_fires_after_initial_delay - Updated to reflect new Telegram timing (15s initial, 30s interval) with additional test cycle

Final checks

I have completed the following:

  • I have followed the Contributing guide.
  • I have performed a self-review of my code and materials.
  • I have made the corresponding changes to the documentation (test comments).
  • My changes generate no new warnings.
  • I have added tests that prove my fix is effective or that my feature works.
  • New and existing unit tests pass locally with my changes.

Additional information

The timing configuration changes are isolated to the integration config file, with corresponding test updates to ensure the new intervals are properly validated. No breaking changes to the API or public interfaces.

https://claude.ai/code/session_01UFauiW8uuB59hJSbq9CnY2

claude added 2 commits March 12, 2026 10:11
WhatsApp: keep immediate first reaction, change interval from 7s to 15s
Telegram: change initial delay from 10s to 15s, interval from 10s to 30s

https://claude.ai/code/session_01UFauiW8uuB59hJSbq9CnY2
@milosmns milosmns merged commit ff8077f into main Mar 12, 2026
3 checks passed
@milosmns milosmns deleted the claude/fix-notifier-timing-LfK2W branch March 12, 2026 11:00
@github-actions
Copy link
Contributor

Build 22998599575 complete for 755fb9e.

# Valid until a new build
docker pull appifyhub/the-agent:latest_pr
docker pull appifyhub/the-agent:5.0.23.pr_328

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.

2 participants