Thanks for the reply. I guess that brings me to the question: If I want a workflow to automatically deactivate, do all the jobs within the workflow and the workflow itself need to have these settings assgined?
-------------------------------------------
Original Message:
Sent: Apr 21, 2026 09:09 AM
From: Marilyn Singley
Subject: Automatically Deactivate Object with OK Status
I have a few workflows that the users want to deactivate no matter what.
This works for me -- in the JOBP -- in the Attributes tab
Set Deactivate on finish to always -- you can choose how many minutes to wait -- and OK status I leave blank.

Original Message:
Sent: Apr 17, 2026 02:19 PM
From: Denison Wood
Subject: Automatically Deactivate Object with OK Status
Hello,
I have reviewed a few threads pertaining to this subject but have lacked answers.
I have objects that find their way to the OK activity status even though their attributes are set to Decativate on Finish: After error free-execution > ANY_OK > 0 min.
If the workflow has this setting and its child objects do not, could this be why the workflow also ends up in that window?
Note, these are the threads I reviewed:
Deactivate "ENDED_OK" jobs in activity window | Automic Workload Automation
How do I cancel A LOT of tasks on the activity window? | Automic Workload Automation
Clear Down the Activity Window using SQL on the Automic Database | Automic Workload Automation
-------------------------------------------