chore: increase vanir-signatures cron job alert threshold to 5 hours#5248
Merged
cuixq merged 1 commit intogoogle:masterfrom Apr 15, 2026
Merged
chore: increase vanir-signatures cron job alert threshold to 5 hours#5248cuixq merged 1 commit intogoogle:masterfrom
cuixq merged 1 commit intogoogle:masterfrom
Conversation
cuixq
changed the title
michaelkedar
approved these changes
Apr 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR increases the
cronLastSuccessfulTimeMinsthreshold for the vanir-signatures cron job from 400 minutes to 660 minutes.The job is scheduled to run every 6 hours (360 minutes). With the previous threshold of 400 minutes, the job was only allowed a 40-minute execution window before triggering an alert.
During periods of high data volume, the job has been observed to take between 4 and 5 hours to complete successfully. This was causing frequent "false positive" alerts even when the job was processing correctly.