Discovery Task status is not Success or Failed on completion

Problem

Some of my Discovery tasks don't post a success or failure status and the SCOM task contains no output aside from “Exit Code:3”:

Cause

This is seen where SCOM terminates the process running the task and can be caused by many things (bad payload, SCOM internal issues) but is most commonly caused by the task running for longer than its configured timeout. If a task runs for longer than its timeout, SCOM kills the process in this way by posting exit code 3.

Solution

This issue is usually solved by extending the task's timeout. This can be done from within the CI map’s configuration:

  1. Navigate to the Administration pane, then to ServiceNow Connector - Cookdown > Discovery

  2. Select the CI type map that is failing in this away and click Modify

  3. Increase the timeout

Search