RealAdvice

WarpCore

WorkFlow PM

/

A task says “Not applicable”

Troubleshooting

A task says “Not applicable”

A value the task depends on does not match its test.

Symptom

A task you expect to do shows Not applicable: on the project's page in the State column, or on its card in the Work panel. It has no Move to… and is not on anyone's My Tasks.

While the value it tests is still empty, its card in the Work panel says Undecided instead, and names the task that asks for the value. That is cause 1 below.

Likely causes

The template says the task applies only when a value of the project passes a test, such as “Client approved the appeal is Yes”. While any of its tests fails, the task is not applicable.

#
Cause
1
The value the task tests is still empty. Every value starts empty, so the task starts not applicable.
2
The value is filled in, but does not pass the test.
3
Someone changed or emptied the value, and the task stopped applying.
No records

Checks

  • Find which values the task tests. On Workflow Templates, open the template and select View on the version the project uses. In its Tasks section, the task's row says Only when and how many tests it has. Select Show to read them.
  • Open the project's page and read those values under Fields. An empty value shows an empty box.

Fix

  1. A department manager enters the value on the project's page. When every test passes, the task becomes Active by itself. See Change a project's values.
  2. The same: a manager corrects the value, if it is wrong.
  3. If the value is right but the task is needed anyway, a manager selects Bring back on its row. See Skip a task, and bring it back.

Before you do this

When a task stops applying, the documents and answers it had asked for are no longer waited for. If it applies again, they show as not yet requested: ask for them again.

Confirm it worked

The task shows Active on the project's page, and is back on the My Tasks of the people on it.

Who to ask

A department manager changes values and brings tasks back. If the test itself is wrong, tell the template's author. A change to a template reaches only the projects started from its new version. See Why a task is “Not applicable”.