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: Too many requests. Which two actions may be used to address this error? (Choose two.)

The "429: Too many requests" error indicates that the API's rate limit has been exceeded. To address this in a high-volume iteration, two primary strategies can be employed. First, a proactive approach is to slow down the rate of requests. Adding a Sleep module (A) inside the iteration introduces a deliberate pause between each API call, preventing the scenario from hitting the rate limit. Second, a reactive approach involves robust error handling. Adding an error handler route to the module (C) allows the scenario to catch the 429 error specifically. This route can then implement logic, such as using a Resume directive combined with a delay, to retry the failed operation after waiting, allowing the rate limit to reset.

B. Use an ignore directive on the module generating the error: This would cause the scenario to skip the failed operation, leading to incomplete or lost data, and it does not resolve the underlying rate-limiting issue.
D. Use a break directive on the module generating the error: This would halt the scenario execution entirely upon encountering the first 429 error, preventing the remaining items in the iteration from being processed.

1. For option A (Sleep module): The "Sleep" module within the "Tools" app is designed to pause a scenario's execution. The documentation states

"The Sleep module allows you to delay the scenario execution for a specified time (in seconds)." This is the standard method for throttling requests to avoid rate-limiting.

Source: Adobe Experience League. "The Tools app in Adobe Workfront Fusion". Section: "Sleep".

2. For option C (Error handling route) and why B/D are incorrect: Advanced error handling allows for specific actions when an error occurs. An error handler route can be added to a module to catch errors. The documentation on error handling directives explains that Ignore skips the error and Break stops the scenario. A more appropriate solution for a 429 error would be a Resume directive in an error handler route

which can be configured to retry the operation after a delay. This aligns with the concept of adding a module/route to handle the service error.

Source: Adobe Experience League. "Advanced error handling in Adobe Workfront Fusion". Section: "Error handling directives".