feat(api): retry configuration for api block

[waleedlatif1]

Summary

add configurable request retries to api block

Fixes #3225

Type of Change

• New feature

Testing

Tested manually

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Feb 25, 2026 8:01am

[greptile-apps]

Greptile Summary

This PR adds configurable retry logic to the API block, allowing users to specify retry attempts, delays, and exponential backoff for handling transient failures like timeouts, rate limits (429), and server errors (5xx).

Key changes:

• Adds four new advanced configuration options: retries count, initial delay, max delay, and non-idempotent retry flag
• Implements exponential backoff with jitter for retry delays
• Respects Retry-After headers from 429 responses
• Only retries idempotent methods (GET, HEAD, PUT, DELETE) by default; POST/PATCH require explicit opt-in
• Properly consumes response bodies before retrying to prevent resource leaks
• Includes comprehensive test coverage for all retry scenarios

Confidence Score: 4/5

• This PR is safe to merge with minor considerations for production usage
• Well-implemented retry logic with proper safeguards (max retry limits, body consumption, idempotency checks). Previous resource leak issue has been addressed. Comprehensive test coverage validates all retry scenarios. Default of 0 retries ensures no behavior change for existing users.
• Pay close attention to apps/sim/tools/index.ts for the retry implementation logic

Important Files Changed

Filename	Overview
apps/sim/tools/index.ts	Implements retry logic with exponential backoff, handles idempotent/non-idempotent methods, and consumes response bodies before retry
apps/sim/tools/http/request.ts	Adds retry configuration parameters with appropriate defaults and visibility settings
apps/sim/tools/index.test.ts	Comprehensive test coverage for retry logic including 5xx, 429, timeouts, idempotency, and Retry-After header handling

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[API Request] --> B{Retry Config Enabled?}
    B -->|No| C[Execute Request Once]
    B -->|Yes| D{Method Idempotent?}
    D -->|Yes| E[Execute Request]
    D -->|No| F{retryNonIdempotent?}
    F -->|No| C
    F -->|Yes| E
    E --> G{Request Successful?}
    G -->|Yes| H[Return Response]
    G -->|No| I{Retryable Error?}
    I -->|No| J[Return Error]
    I -->|Yes| K{Attempts Remaining?}
    K -->|No| J
    K -->|Yes| L{429 with Retry-After?}
    L -->|Yes| M{Retry-After > maxDelay?}
    M -->|Yes| J
    M -->|No| N[Wait Retry-After]
    L -->|No| O[Calculate Backoff]
    N --> E
    O --> P[Wait with Jitter]
    P --> E
    C --> Q{Success?}
    Q -->|Yes| H
    Q -->|No| J

Loading

_{Last reviewed commit: 3b1fd86}

[greptile-apps]

_{7 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[greptile-apps]

_{7 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[waleedlatif1]

@cursor review

[waleedlatif1]

@greptile

[greptile-apps]

_{7 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[waleedlatif1]

@cursor review

[waleedlatif1]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR