A Fusion designer is unhappy with the high number of bundles passing through an instant Watch Events module that monitors Workfront project updates. Which action reduces the number of bundles passing through the module?

The "Watch Events" module is an instant trigger that uses webhooks. It executes for every subscribed event in Workfront, which can generate a high volume of bundles if updates are frequent. To solve this, changing the module to "Watch Record" is the most effective action. The "Watch Record" module is a polling trigger that allows the designer to specify filter criteria. This configuration ensures that the scenario is only triggered for records that meet specific conditions, directly reducing the number of bundles created and processed, thus lowering operation consumption.

A. The "maximum number of returned events" setting is a feature of polling triggers, not the instant "Watch Events" module, which processes events one by one as they occur.
B. Reducing the maximum number of cycles only limits how a scenario processes a batch of bundles already received; it does not decrease the number of bundles the trigger initially receives.

1. Adobe Experience League Documentation, "Trigger modules in Adobe Workfront Fusion." This document distinguishes between instant triggers (like Watch Events) and scheduled (polling) triggers (like Watch Records). It states, "Instant triggers... immediately trigger a scenario when they receive data," implying they process every event. In contrast, scheduled triggers run at intervals, which is characteristic of modules like "Watch Records" that can be configured to pull only specific data. (See section: "Types of trigger modules").

2. Adobe Experience League Documentation, "Adobe Workfront modules." This page details the functionality of different Workfront modules. The description for polling triggers like "Watch Records" inherently involves querying for records that meet certain criteria (new or updated since the last check), which is the basis for filtering. The "Watch Events" module is described as an instant trigger that "returns a notification when an event occurs," without mentioning any built-in filtering mechanism. (See section: "Triggers").