Skip to content

Batch processing won't retry failures in same way as non-batch requests get retried #2660

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
DeveloperRob opened this issue Mar 12, 2025 · 0 comments

Comments

@DeveloperRob
Copy link

When sending a single request (which includes the batch 'wrapper' request), if a number of different errors occur (including rate limiting), {{src/Task/Runner.php}} will by default retry the request following Google's recommended exponential backoff tactic.

However, when making a backup request, it is possible that within the batch there will be a mix of 200 responses and non-200 responses. In this instance, {{execute}} will return an array that contains the valid responses alongside the exceptions.

In the event that the user requires all valid responses before continuing, they need to implement their own userland logic that iterates over the responses, identifies those that failed, and then reattempts a second batch with just the failures (after the backoff delay). Given that the project contains logic for retrying a single request, it would be useful if this was supported (always or optionally) for batch requests.

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

No branches or pull requests

1 participant