In Adobe Workfront, a task's 'Percent Complete' and its 'Status' are distinct fields. A project cannot be set to 'Complete' if any of its tasks have a status that does not equate to a complete state (e.g., 'In Progress', 'New'), even if those tasks show 100% in the 'Percent Complete' field. The system error occurs because the project's completion is gated by the task status, not just the percentage. The Project Owner must identify tasks that are 100% complete but still have an active status and update their status to 'Complete' or an equivalent. Filtering the task list for incomplete tasks is the correct procedure to locate them.

A. While an incomplete approval can prevent a task's status from being updated, the direct cause of the project-level error is the task's status itself, not the pending approval.

B. This option incorrectly focuses on project issues. The question specifically asks how to determine which tasks are incomplete, not which issues are open.

1. Adobe Workfront Documentation

"Update the status of a project": This document outlines the prerequisites for changing a project's status. It explicitly states

"You cannot mark a project Complete if there are incomplete tasks or open issues on the project." This directly supports the error message received by the user and the core problem. (Source: Adobe Experience League

Workfront Documentation

Projects section).

2. Adobe Workfront Documentation

"Overview of Task Status": This article explains the difference between system statuses. It clarifies that statuses like 'New' and 'In Progress' represent incomplete work

whereas the 'Complete' status signifies that the task is finished. This distinction is central to the question

as a task at 100% can still have an 'In Progress' status. (Source: Adobe Experience League

Workfront Documentation

Tasks section).

3. Adobe Workfront Documentation

"Edit tasks": In the section detailing task fields

the documentation describes 'Percent Complete' and 'Status' as separate

editable fields. It notes that setting a task's status to 'Complete' automatically sets the 'Percent Complete' to 100%. However

the reverse is not a default behavior; setting 'Percent Complete' to 100% does not automatically change the status to 'Complete'

which is the root cause of the scenario in the question. (Source: Adobe Experience League

Workfront Documentation

Tasks section).