A Fusion scenario updates project conditions each night, and should set the project condition to At Risk if there are any high priority open issues…

The root cause of the problem is that the update action is placed inside the iterator that cycles through every issue, leading to multiple, potentially conflicting updates for a single project. By creating a separate scenario dedicated to the update action, the developer can enforce the single responsibility principle. The original scenario's responsibility would be to iterate through projects and their issues to identify if the "At Risk" condition is met. Upon confirmation, it would make a single call (e.g., using a webhook) to the second scenario, passing the project ID. This ensures the update operation is executed only once per project, resolving the issue.

A. This is logically flawed. If the search for issues is not pre-filtered by priority, retrieving only the "First Matching" issue could cause the scenario to miss a high-priority issue later in the list.
B. An error handler manages module failures (e.g., a connection timeout). It does not control the intended logical flow or the number of times a module executes within an iterator.
D. Adobe Workfront Fusion does not have a specific flow control module or function named "Run Once." While the concept is achievable with other tools, this option refers to a non-existent feature.

1. Correct Answer Rationale (Calling Scenarios): Adobe Experience League. "Call another scenario from a scenario in Adobe Workfront Fusion." This document outlines the use of Webhooks or the "Run a Scenario" module to create modular, reusable scenarios, which supports the architectural solution proposed in option C.

2. Incorrect Option A Rationale (Search Logic): Adobe Experience League. "Search for records module in Adobe Workfront Fusion." This documentation details search module configurations. It clarifies that limiting results without proper filtering criteria can lead to incomplete data processing, which is the logical flaw in option A.

3. Incorrect Option B Rationale (Error Handling): Adobe Experience League. "Error handling in Adobe Workfront Fusion." This guide explains that error handler directives (like "Ignore") are for managing unexpected module failures, not for implementing conditional logic or controlling iteration flow.

4. Incorrect Option D Rationale (Flow Control): Adobe Experience League. "Flow control in Adobe Workfront Fusion." This page provides a comprehensive list of available flow control modules, such as Iterator, Router, and Array Aggregator. A "Run Once" module is not listed, confirming that option D refers to a non-existent tool.