When configuring a scan within AppCheck, it is possible to set the configure scan to launch multiple instances on a repeating schedule (say, once per week every week from the time of the initial instance launch).
Sometimes a repeating (scheduled) scan instance may fail to launch as expected. Since future (repeating) scan instances are launched automatically on schedule, as opposed to manually via the web admin interface, you may need to login to the scan portal to check that the scan has launched correctly if you do not receive a scan completion notification as expected.
Below is a list of the most common reasons why a scheduled scan may fail to run. If none of these explains your case, then please contact AppCheck Technical Support via https://appcheck-ng.com/get-help/contact-support/.
Reason 1 - Your account may already be running the maximum number of concurrent scans
There is a limit on how many scans your organisation is licensed to run concurrently. If this limit is exceeded at any given time, then a scheduled scan may fail to launch as expected. For more information on this behaviour, please see our knowledgebase article at:
Reason 2 - There may be a problem with one or more of the scan targets
It is also possible that there is a problem with one or more of the configured scan targets. Specific issues that may prevent a scan instance from launching against a configured target include:
- The target cannot be resolved - that is, the scanner was not able to resolve the provided FDQN (domain or hostname) to an IP address. In order to resolve this:
- For public targets make sure the FQDN can be resolved in public DNS.
- For internal targets add a hosts entry in https://scanner.appcheck-ng.com/scan_hubs.
- The target listed is not within your licensed account scope. In order to resolve this:
- Contact AppCheck Support to request that they add the scan targets to your account scope. You can contact AppCheck Technical Support at https://appcheck-ng.com/get-help/contact-support/
Targets with a problem will be marked with a warning sign (an exclamation mark in a triangle) in your scan configuration. The type of problem is colour-coded. The key below the Targets box explains what each colour means, as shown below: