Discovery Fundamentals Simulator fails validation module 4 task 2 error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2025 03:28 AM
On discovery fundamentals simulator in module 4 on "task: Create Discovery Schedule", Im getting task result failed, desipte getting all the correct results in the instance. I cant figure out whats the error.
Ive completed the vertification steps:
1. A windows server named ip-198-51-12-119 is discovered.
2. A linux server named ip-198-51-188-74 is discovered.
3. On Discovery dashboard, there are 2 newly discovered windows servers and 1 linux server in the last 7 days.
In addition, Ive checked that the Discovery Schedule are named correctly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2025 04:18 AM
Hi @Ole-KristiaT ,
Share the task requirement.
-------------------------------------------------------------------------
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
02-02-2025 01:10 PM
Could you please share a screenshot of the task failure during validation? It would help in providing more specific guidance.
In general , If any task result fails during validation, you will be presented with feedback text indicating the possible cause of the failure, along with clickable links to the ServiceNow documentation site for additional guidance.
The verification steps that you mentioned is correct and are matching to the expected result ..
I am assuming, since I don’t have a screenshot (shared by you) or access to your instance, that the issue could be related to the previous dependent task step. Specifically, the credential validation should have been completed earlier. If you missed that step, it could result in an error when you try to perform validation in the next step..
----------