Conversation
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
1 participant
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.
The catalog build is supposed to run every 30mins, however this morning it had not been run for 12 hours despite there being new nodes.
I think the problem is the timings, the action is scheduled to run at 0 and 30 mins past the hour
GitHub's scheduled workflows are best-effort with no guarantee: the schedule event gets delayed during high load, and under enough load it's dropped entirely, not just deferred. And */30 lands on the two single most popular scheduling times on all of GitHub, so :00 and :30 are the most congested and the most likely to be delayed or skipped. We don't see any failures in the actions log it just looks like the job gets skipped.
This PR adjusts the times to 07 and 37 which will hopefully avoid some of the peak rush times on jobs and improve the sucess.