Overview

Internal scans can take longer than expected when one or more targets are offline or unreachable. The scanner keeps retrying those targets while everything else sits waiting, so a single powered-off laptop can hold up an otherwise finished scan.

The internal target response timeout controls how long Intruder waits for an unresponsive target before skipping it and completing the scan. This article covers where to set it, and what happens to a target that gets skipped.

What happens when the timeout is reached

Any internal targets still unreachable are skipped, and the scan completes for everything that responded. Results are returned as soon as scanning finishes for the reachable endpoints — a skipped target no longer holds up the run.

A skipped target is marked unresponsive for that run only. It reverts to Active automatically on the next scan where it responds, and its findings and remediation history are unaffected.

The three timeout options

You can choose from the following predefined options:

2 hours - Prioritise speed (default)
6 hours - Balanced
12 hours - Prioritise coverage

Shorter windows return results faster and skip more targets; longer windows cover more of your estate but take longer to complete.

Setting the account-wide default timeout

Navigate to Scans > Settings >
Internal target response timeout
Select your preferred timeout (2h, 6h, or 12h)

Setting the timeout for an ad-hoc or scheduled scan

Individual scans can override the account default using the Internal target timeout control under Advanced settings. An override always wins — the account default applies only where no override is set.

Scan Type	Steps	Screenshot
New scheduled scan	Navigate to Scans. Click Schedule scan to edit your scheduled scan. Expand the Advanced settings. Select your preferred timeout (2h, 6h, or 12h).
Existing scheduled scan	Navigate to Scans. Click '•••' > Edit to edit your scheduled scan. Expand the Advanced settings. Select your preferred timeout (2h, 6h, or 12h).
Ad-hoc scan	Navigate to Scans. Click Scan now. Expand the Advanced settings. Select your preferred timeout (2h, 6h, or 12h).

Troubleshooting

Some targets were skipped
See Why is my internal system showing as unresponsive? for troubleshooting steps.

A target shows as unresponsive after I fixed it
Being skipped doesn't affect a target's findings or remediation history. It returns to Active automatically on the next scan where it responds.

I can't see the setting
You must be on a Pro, Enterprise, or Vanguard plan, and have the Admin or Scan user role.

FAQ

When should I select a shorter timeout?
A shorter window may be useful if you frequently run remediation or verification scans, most of your endpoints are expected to be online, or you want predictable scan completion times.

When should I select a longer timeout?
A longer window may be useful if endpoints come online intermittently, you want to maximise coverage in a single run, or scans are scheduled overnight or during low-impact periods.

Will the internal target response timeout impact my external scans?

No, the internal target response timeout only applies to scans of internal targets.

If an internal target is skipped, will it be scanned in the future?

Yes, provided it's responsive during future scans.

If I set both an account default and a per-scan override, which applies?
The override. The account default applies only to scans without one.

Does changing the account default affect scans that already have an override?
No, those scans keep their specified timeout value until you change it.

Internal Target Response Timeout