Skip to content

Reverting local change#13804

Merged
KarnaiahPesula merged 1 commit into
developmentfrom
bugfix-reverting-local-cron-change
Jan 23, 2026
Merged

Reverting local change#13804
KarnaiahPesula merged 1 commit into
developmentfrom
bugfix-reverting-local-cron-change

Conversation

@KarnaiahPesula
Copy link
Copy Markdown
Contributor

@KarnaiahPesula KarnaiahPesula commented Jan 23, 2026

Fixes #

Summary by CodeRabbit

  • Chores
    • Modified external message synchronization schedule to run once daily at a fixed time rather than every 2 minutes.

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jan 23, 2026

📝 Walkthrough

Walkthrough

The fetchExternalMessages() method in CronService now executes once daily at 01:35:00 instead of every 2 minutes, achieved through modification of the @Schedule annotation. No functional code changes.

Changes

Cohort / File(s) Summary
Cron Schedule Configuration
sormas-backend/src/main/java/de/symeda/sormas/backend/common/CronService.java
Updated @Schedule annotation on fetchExternalMessages(): changed from every 2 minutes (hour = "", minute = "/2", second = "0") to daily at 01:35:00 (hour = "1", minute = "35", second = "0")

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • tb review result updates #13572: Modifies the same @Schedule annotation on CronService.fetchExternalMessages() with an identical trigger time change to 01:35

Poem

🐰 Tick-tock, tick-tock, no more every two,
Now at dawn's early hour, 01:35 will do,
Messages fetch but once per day,
A gentler schedule, hip-hooray! 🕐

🚥 Pre-merge checks | ❌ 3
❌ Failed checks (2 warnings, 1 inconclusive)
Check name Status Explanation Resolution
Description check ⚠️ Warning The description contains only the template comment and an empty 'Fixes #' placeholder with no issue number or explanation of the revert. Complete the description by specifying the issue number and explaining why the local cron scheduling change is being reverted.
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
Title check ❓ Inconclusive The title 'Reverting local change' is vague and generic, failing to convey meaningful information about the specific change being reverted. Make the title more specific by indicating what was reverted, such as 'Revert CronService fetchExternalMessages scheduling change' to clearly convey the change.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@sormas-vitagroup
Copy link
Copy Markdown
Contributor

@KarnaiahPesula KarnaiahPesula merged commit c81b6ef into development Jan 23, 2026
8 of 10 checks passed
@KarnaiahPesula KarnaiahPesula deleted the bugfix-reverting-local-cron-change branch January 23, 2026 09:38
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.

3 participants