Merged
Conversation
onmax
temporarily deployed
to
preview-testnet
GitHub Actions
Inactive
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
validators-api-main | 4bc2c21 | Commit Preview URL Branch Preview URL |
Feb 26 2026, 07:26 AM |
onmax
temporarily deployed
to
preview-testnet
GitHub Actions
Inactive
Member
|
❌ Fix the error |
Albermonte
approved these changes
Feb 25, 2026
Member
Albermonte
left a comment
Albermonte
left a comment
There was a problem hiding this comment.
I guess you have tested and it works
Member
Author
|
@codex review |
…tolerance # Conflicts: # server/utils/validators-bundle.ts
onmax
temporarily deployed
to
preview-testnet
GitHub Actions
Inactive
onmax
temporarily deployed
to
preview-testnet
GitHub Actions
Inactive
onmax
temporarily deployed
to
preview-testnet
GitHub Actions
Inactive
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.
We tracked this down: we recently changed the policy to allow up to 1 epoch of lag for validator scores. Cron jobs are running successfully at 00:00 and 12:00 UTC, but epochs are about 11.8 hours long (not exactly 12h), so a 1-epoch delay can happen even when sync is healthy.
The real issue was that the status health check treated that 1-epoch lag as an error. This PR updates the logic so it only reports an error when lag reaches 2 or more epochs.
It also adds status diagnostics (
latestScoreEpoch,scoreLagEpochs,allowedScoreLagEpochs), updates dashboard copy to reflect the 12h schedule, and aligns README wording.