A custom API call to a web service is used inside of a high volume iteration. The module that calls the web service sometimes returns an error - 429…

When encountering the error 429: Too many requests, which indicates the web service is being

overwhelmed by requests, the following actions can help:

A . Add a Sleep Module:

Adding a Sleep module introduces a delay between iterations, reducing the frequency of API calls.

By slowing down the rate of requests, you avoid hitting the rate limits of the web service, thus

reducing the chances of receiving a 429 error.

This approach is useful for managing high-volume iterations without overloading the external

service.

C . Add a Module to Test the Service for Errors:

Adding a module to test the service's response before making a call can help prevent the 429 error

by checking if the service is ready to handle requests.

This preemptive check allows the scenario to conditionally execute, ensuring that it doesn't

overwhelm the service and respects the API rate limits.

Why Not Other Options?

B . Use an Ignore Directive: Ignoring errors can be risky because it would cause the scenario to ignore

429 errors, possibly leading to failed API calls that are not addressed. Ignoring an error doesn’t solve

the issue of too many requests being sent to the service.

D . Use a Break Directive: The Break directive would stop the execution, which is counterproductive

when trying to resolve the issue by reducing the rate of requests. It would not address the root cause

of too many requests.

Reference:

Adobe Workfront Fusion Documentation: Handling API Rate Limiting with Sleep and Error Handling

Experience League Community: Managing Web Service Errors in High-Volume Iterations