-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add alert delays to daily runs #113
Conversation
@@ -94,8 +95,8 @@ def update_ridership(event): | |||
ridership.ingest_ridership_data() | |||
|
|||
|
|||
# 7:20am UTC -> 2:20/3:20am ET every day | |||
@app.schedule(Cron(20, 7, "*", "*", "?", "*")) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reducing runs to reduce AWS cost slightly since it shouldn't serve any benefit
# 9:00 UTC -> 4:00/5:00am ET every weekday. | ||
# This is the last job that runs for the day. | ||
# No need to run on weekends | ||
@app.schedule(Cron(0, 9, "?", "*", "MON-FRI", "*")) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reducing runs to reduce AWS cost slightly since it shouldn't serve any benefit
In prep for transitmatters/t-performance-dash#997 we should update the backfill weekly (with a lookback of 8 days)
There's no benefit to running more than once a week since we scrap partial weeks