Where can I find Job Log for a Scheduled Job that ran?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2024 11:01 PM
Where can I find Job Log for a Scheduled Job that ran?
I read in this post that I can find them in syslog_transaction, but its not logged for all the jobs.
https://www.servicenow.com/community/developer-forum/scheduled-job-history-log/m-p/1698439
Evidence:
OOB auto close incident job is active and running every one hour
but nothing is logged in syslog_transaction table
Strange thing is, I have another scheduled job which also runs repeatedly
and this is getting logged in syslog_transaction table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2024 11:20 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-19-2024 12:32 AM
Hi @Harish Bainsla that did not answer my query 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2024 11:25 PM
Hi @Suggy ,
It will show the result if it is in radar to run today. I have changed the next action for today date and time then its start appearing in todays job
-------------------------------------------------------------------------
If you found my response helpful, please consider selecting "Accept as Solution" and marking it as "Helpful." This not only supports me but also benefits the community.
Regards
Runjay Patel - ServiceNow Solution Architect
YouTube: https://www.youtube.com/@RunjayP
LinkedIn: https://www.linkedin.com/in/runjay
-------------------------------------------------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-19-2024 12:33 AM
@Runjay Patel Yes I am aware of it. but that is not logging the job execution details in syslog_transaction table even though the job ran several times today. You can check in your instance 🙂