Archive service alert: fix success email schedule #493
+10
−27
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
qzhodl
reviewed
Jan 19, 2026
| send=true | ||
| elif [[ "$EVENT_NAME" == "schedule" ]]; then | ||
| hour_utc="$(date -u +%H)" | ||
| if [[ "$hour_utc" == "00" ]]; then |
Collaborator
There was a problem hiding this comment.
I’m still not clear on what caused the email sending failure—could you clarify the root cause?
Collaborator
Author
There was a problem hiding this comment.
The email was scheduled at 0 UTC and used the timestamp to match the hour. However, due to busy workflow schedue, it already 1+ UTC when the workflow actually started, so the condition did not match.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 daily success email was not sent due to GitHub's delayed schedule. Replace it with a more reliable matcher, and also avoid peak hours for the schedule.