Discovery logs show "Canceled discovery of <schedule name>. Already at maximum number of active 'Scheduled' invocations (3) for a given schedule" - Support and Troubleshooting

Discovery logs show "Canceled discovery of . Already at maximum number of active 'Scheduled' invocations (3) for a given schedule" Issue  Canceled discovery of . Already at maximum number of active 'Scheduled' invocations (3) for a given schedule

Issue After several scheduled discovery tasks are run, the Discovery logs show the following error message:

Canceled discovery of . Already at maximum number of active 'Scheduled' invocations (3) for a given schedule

This message represents the maximum number of scheduled invocations of the same Discovery schedule. This prevents a backlog of scheduled runs if Discovery does not finish before the next invocation is scheduled to run. If the limit (3) has been reached, subsequent scheduled invocations are canceled.

Note : You can change the default value in the system properties as described in the product documentation topic Configure Dscovery properties .

Workaround Navigate to Discovery > Status and filter the following fields:

Schedule: State: Active Run the filter.

If three entries are returned, that is the cause of the maximum number of active invocations message. Either cancel the active discoveries or identify why the active discoveries are not completing in a timely manner.