# A pipeline call to a tax API has max_attempts=5 and a 60-second cap; the naive worst case is 1+2+4+8

Canonical URL: <https://datadriven.io/problems/a-pipeline-call-to-a-tax-api-has-maxattempts5-and-a-60-sec-536bd765>

Domain: Pipeline Design · Difficulty: medium

## Problem

A pipeline call to a tax API has max_attempts=5 and a 60-second cap; the naive worst case is 1+2+4+8+60=75 seconds. In production the calls themselves time out at 30 seconds each, the cap fires on the 60-second waits, and actual elapsed retry time runs to several minutes. The section names five numbers a complete retry budget defines: max_attempts, base_delay, max_delay, max_total_elapsed, and jitter. Set the budget by replacing the retry transform with one whose name states all five.

## Related

- [All practice problems](https://datadriven.io/problems)
- [Mock interview mode](https://datadriven.io/interview/a-pipeline-call-to-a-tax-api-has-maxattempts5-and-a-60-sec-536bd765)
- [System Design Interview Questions](https://datadriven.io/data-engineering-system-design)
- [Data Engineering Interview Prep Guide](https://datadriven.io/data-engineer-interview-prep)
- [Daily Challenge](https://datadriven.io/daily)

---

Source: DataDriven (https://datadriven.io). 100% free data engineering interview prep. Live code execution against Postgres 16, Python 3.11, and Spark sandboxes. No paywall, no premium tier, no signup gate.