Poll for run completion every 5 minutes instead of checking once
All checks were successful
Deploy / deploy (push) Successful in 28s
All checks were successful
Deploy / deploy (push) Successful in 28s
The one-shot VERIFY_DELAY_MINUTES check was too rigid: MassPrice's processing time varies widely in practice (observed ~1 to over 20 minutes, and its queue can back up further under load — confirmed live, a run still sitting in "Queued" 15+ minutes in), so a single check window either misses slow-but-fine completions or has to be set needlessly long. Replaced with a poll loop: scheduler.py reschedules another one-off check every VERIFY_POLL_MINUTES (default 5) until automation's check_completion() reports "complete", up to VERIFY_MAX_ATTEMPTS (default 12, ~1 hour) before giving up and marking "not_confirmed" for good. verify_run() is split into a pure check_completion() (no storage side effects) so scheduler.py's loop owns the retry/give-up decision; automation.py just answers "is it done yet". Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01H6TgffxTvYhqxykAbVQg2v
This commit is contained in:
parent
8b58dadc5a
commit
213837ff97
6 changed files with 151 additions and 90 deletions
|
|
@ -16,7 +16,8 @@ services:
|
|||
- LOGIN_PASSWORD=${LOGIN_PASSWORD}
|
||||
- SECRET_KEY=${SECRET_KEY}
|
||||
- TZ=${TZ:-America/Phoenix}
|
||||
- VERIFY_DELAY_MINUTES=${VERIFY_DELAY_MINUTES:-10}
|
||||
- VERIFY_POLL_MINUTES=${VERIFY_POLL_MINUTES:-5}
|
||||
- VERIFY_MAX_ATTEMPTS=${VERIFY_MAX_ATTEMPTS:-12}
|
||||
- GMAIL_USER=${GMAIL_USER:-}
|
||||
- GMAIL_APP_PASSWORD=${GMAIL_APP_PASSWORD:-}
|
||||
- ALERT_EMAIL=${ALERT_EMAIL:-}
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue