Indefinitely retry to fetch #3088

Activity

1. rekram1-node

   self-assigned this

   on Oct 11, 2025
2. github-actions commented on Oct 11, 2025

   

   github-actionsBot

   on Oct 11, 2025 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • More resilient retry policy for Amazon Bedrock rate limiting #452: More resilient retry policy for Amazon Bedrock rate limiting - discusses retry mechanisms and suggests more resilient retry policy instead of just trying 3 times
   • Implement exponential back-off when hitting rate limits #1712: Implement exponential back-off when hitting rate limits - specifically mentions exponential back-off with auto-retry to keep agent loop running
   • handle LLM overload errors (e.g. {"type": "overloaded_error", "message": "Overloaded"}) #833: handle LLM overload errors (e.g. {"type": "overloaded_error", "message": "Overloaded"}) - proposes retry logic with limits to avoid infinite loops, very similar concept
   • Implement retry with backoff #1321: Implement retry with backoff - directly mentions implementing retry with backoff functionality

   These issues all discuss implementing better retry mechanisms with proper backoff strategies to avoid the exact problem you're experiencing with indefinite retries on 404 status codes.

   Feel free to ignore if none of these address your specific case with 404 status codes and URL fetching.
3. rekram1-node commented on Oct 11, 2025

   

   rekram1-node

   on Oct 11, 2025

   Last edited by rekram1-node

   Contributor

   More actions

   edit: wow yeah ill fix this
4. thdxr

   closed this as completedon Mar 25, 2026