Task.Status — state machine

Task State Machine — Status

Generated 2026-04-22T08:21:15.509Z via PWG Salesforce MCP. Shows the 7 active Status values and which Flows fire when a record is in each stage.

State diagram

Shows stage-specific Flow hits. A Flow binding of ‘any’ means it’s triggered on every Create/Update with no stage filter — shown in the ‘Any stage’ swimlane below.

Flows per stage (StageName EqualTo)

Stage	Flows that fire while in this stage
Open (Open)	—
Not Started (Not Started)	—
In Progress (In Progress)	—
Waiting for Further Information (Waiting for Further Information)	—
Completed (Completed)	Action After Initial Client Contact Task TEMP Task Opportunity Populate Application Set Date
Canceled (Canceled)	—
Failed (Failed)	—

Flows filtered by ‘NotEqualTo’ stage (fire on every stage EXCEPT)

None.

Flows with no stage filter (fire on ANY stage change)

These flows will execute regardless of which stage the record is in. They’re the most dangerous for run-order and recursion issues.

Flow	Trigger	Creates Tasks	Updates Objects
Redemptions - Confirm Redemption Task For ETA	AutoLaunchedFlow	—	—
Task - Actions on After Update	Update	—	Case
Task - Push ETA to Opportunity	Update	—	Opportunity
WM_MF_Task_AFU_After_Update	Update	—	—
WM_MF_Task_ONC_On_Create	Create	—	—

Stages with ZERO Flow hits (potentially unused)

6 active stage value(s) have no Flow filtered to them by EqualTo. Either they’re handled by ‘any-stage’ Flows, by Apex triggers, or they’re dead picklist values.

Stage	Label	Default?
Open	Open
Not Started	Not Started	✓
In Progress	In Progress
Waiting for Further Information	Waiting for Further Information
Canceled	Canceled
Failed	Failed