✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Greptile Overview

Greptile Summary

This PR corrects a critical configuration error where the PKI alert V2 processing queue was mistakenly scheduled to run every minute (* * * * *) instead of once daily at midnight UTC (0 0 * * *).

Key Changes:

• Fixed cron schedule in queueService.schedulePg() call on line 214
• Restores intended behavior: job named DailyPkiAlertV2Processing should run daily, not every minute
• Prevents unnecessary database queries, alert evaluations, and potential performance degradation

Background:
The every-minute schedule was used for testing during development of the PKI-100 feature branch. While it was fixed in commit bb6b1940d, the fix didn't make it into the feature branch before it was merged to main, reintroducing the testing configuration.

Confidence Score: 5/5

• This PR is completely safe to merge - it's a single-character configuration fix that restores intended behavior
• The change is trivial, well-understood, and critical to fix. It only modifies a cron schedule string from every minute to daily, matching the function name and deduplication logic that assumes daily execution. No logic changes, no security concerns.
• No files require special attention

Important Files Changed

@carlosmonastyrski, thanks for taking the time to test my code! I know it ended up being more work than expected.