TASK: IGDB ETL – Retry & Backoff Strategy Implementation

[AndersonGACFilho]

Summary

Implement a simple retry and exponential backoff strategy for transient network errors when communicating with the IGDB API.

Details

• Wrap API calls in a retry loop.
• If a request fails with a transient error (e.g., 5xx status code), the ETL should wait for a short, increasing interval before trying again.
• After a configurable number of retries, it should fail the run.

Acceptance Criteria

• The ETL retries failed API calls.
• The delay between retries increases exponentially.
• The ETL gives up after a set number of attempts.
• Tests updated/added (unit/integration)
• No linter / build errors

Dependencies

• IGDB ETL – Batch Fetch Full Records

Out of Scope

• Complex circuit breaker patterns.

Test Plan

• Write a test that mocks the IGDB API to return a series of 500 errors followed by a 200 success, and verify that the ETL retries and eventually succeeds.

Checklist

• Labels added (task, component/igdb-etl)
• CHANGELOG updated if user-visible
• No secrets committed