active setting false on sc task
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2025 10:30 AM - edited 01-09-2025 10:32 AM
Hi All,
I am creating SC Task from workflow and when I see history of task the active is setting false and then changing to true at same time without even taking seconds of time and also the old value for both is empty.
Can anyone tell what will be the reason behind this?
Please refer to the below screenshot

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2025 11:55 AM
Try checking the code in your workflow action that creates the task and make sure you aren't setting the active flag to false or setting the state to a completed state.
If that looks okay, then maybe check and see if you have any business rules running on it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2025 10:07 PM
I have checked workflow and business rule, nothing is setting active to false and its an intermittent issue.
Only for few tasks active is setting false
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2025 10:38 PM
did you check default value in dictionary?
Did you check BR or it's a calculated field with value as false?
The active=false during creation is in which user's session? is it system?
Since you told it's an intermittent issue then definitely something custom is working on it.
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2025 10:52 PM - edited 01-09-2025 10:57 PM
Hi @Ankur Bawiskar ,
Thanks for your response.
I have checked the default value in the dictionary and all the other you mentioned, but there is nothing that is setting it to false.
To answer your question, it is in the user session of the person who is opening the task.