Skip to content

fix(aave): add retry logic to Graph API query in proposals#200

Merged
spalen0 merged 3 commits intomainfrom
fix/aave-proposals-retry
Apr 4, 2026
Merged

fix(aave): add retry logic to Graph API query in proposals#200
spalen0 merged 3 commits intomainfrom
fix/aave-proposals-retry

Conversation

@spalen0
Copy link
Copy Markdown
Collaborator

@spalen0 spalen0 commented Apr 4, 2026

Summary

  • The Graph gateway can return transient 504 timeouts, crashing the GH Actions workflow (failed run)
  • Replaced raw requests.post() in run_query() with existing request_with_retry() from utils/http — retries with exponential backoff on 5xx, connection errors, and timeouts
  • On failure after retries, logs the error and returns gracefully instead of raising an exception

Test plan

  • Verify GH Actions workflow passes on next run
  • Confirm transient Graph API failures no longer crash the workflow

🤖 Generated with Claude Code

spalen0 and others added 3 commits April 4, 2026 11:25
The Graph gateway can return transient 504 timeouts which crashes the
entire GH Actions workflow. Use existing request_with_retry from
utils/http to retry with exponential backoff, and return gracefully
on failure instead of raising.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Same issue as aave/proposals — direct requests.post() with no error
handling will crash the workflow on transient Graph API failures.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Send a low-priority (silent) telegram notification when Graph API
queries fail after all retries, so the team is aware without being
disrupted.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@spalen0 spalen0 merged commit fe38061 into main Apr 4, 2026
2 checks passed
@spalen0 spalen0 deleted the fix/aave-proposals-retry branch April 4, 2026 09:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant