- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-04-2022 07:47 AM
Hi,
I made the user active yesterday. But today the same user changed to inactive because of Systemscheduler
In sys_user table, some scheduled job/script is automatically updating the active value as false based on some flag value.
I want to find out the scheduled job so that I can change that flag and fix this issue.
How can I findout the schedule job/ is this because of any OOB schedule job ?
-Tried to find the schedule job name using sysid in logs but that is not working
Thanks,
Dinesh
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-04-2022 07:56 AM
Hi,
Things to check
1) Any schedule job is doing this
2) Any LDAP integration is in place which is marking it inactive based on AD
3) Any flow is doing this
4) Any scheduled workflow is doing this
Regards
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-04-2022 07:49 AM
Hi Dinesh,
That's a tough job to do, you can find out a few suggestions mentioned as an example :
Mark my answer correct & Helpful, if Applicable.
Thanks,
Sandeep
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-04-2022 07:56 AM
Hi,
Things to check
1) Any schedule job is doing this
2) Any LDAP integration is in place which is marking it inactive based on AD
3) Any flow is doing this
4) Any scheduled workflow is doing this
Regards
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-04-2022 10:30 AM
This can be a maddening task. A couple of thoughts:
1. If sys_user is audited, check the history of the record to find the exact time of the update and the user who made the update. Then look for jobs which could be running about the time and which run as the user who made the update. Examining the start times of the scheduled jobs is a start, Also, looking at the system log can be a help. Filter the log by the user who made the update.
2. If you're sure it's a scheduled job doing it, then look for scheduled jobs which might update the active field in the user record. Here's a link to get some candidates:
https://YOURINSTANCE.service-now.com/sysauto_list.do?sysparm_query=active%3Dtrue%5Eref_sysauto_script.scriptLIKEsys_user%5Eref_sysauto_script.scriptLIKEactive%5Eref_sysauto_script.scriptLIKEtrue&sysparm_view=
3. The change could be a side effect of another update going on, Check the business rules to see if they might be the ones updating the active field. Here's a link to get candidates for this:
https://YOURINSTANCE.service-now.com/sys_script_list.do?sysparm_query=active%3Dtrue%5EscriptLIKEsys_user%5EscriptLIKEactive%5EscriptLIKEtrue&sysparm_view=