A Fusion designer is unhappy with the high number of bundles passing through an instant Watch Events module that monitors Workfront project updates…

Understanding the Issue:

The Watch Events module is generating a high number of bundles because it monitors a broad range

of project updates in Workfront, resulting in an overwhelming amount of data passing through the

scenario.

The goal is to reduce the number of bundles by narrowing the scope of monitored events.

Why Option C is Correct:

Switching to Watch Record:

The Watch Record module allows users to monitor specific records (e.g., projects, tasks) with

additional filtering options in the criteria or filter box.

By applying filters, the module can focus only on relevant updates, significantly reducing the number

of bundles being processed.

Example: Filtering for specific project statuses, update types, or assigned users ensures that only

relevant changes are captured.

Why the Other Options are Incorrect:

Option A ("Reducing the maximum number of returned events on the trigger"):

This limits the number of bundles processed per cycle but does not address the root cause, which is

the broad monitoring scope of the Watch Events module.

Option B ("Reducing the maximum number of cycles in scenario settings"):

The number of cycles determines how many iterations the scenario performs in one run but does not

reduce the number of bundles entering the scenario.

Steps to Use the Watch Record Module:

Replace the Watch Events module with Watch Record.

Specify the record type to monitor (e.g., Project).

Use the optional filter box to apply criteria, such as specific project fields, statuses, or other

conditions.

Activate the scenario to test the refined data flow.

Reference and Supporting Documentation:

Adobe Workfront Fusion: Watch Record Module

Workfront Community: Managing High Bundle Volumes in Fusion