For a given scan, what causes the “Run Scan Now” option in the more options menu on the Scans page to be unavailable?

The most common causes of this problem include the following:

1. Role-Based Access Control (RBAC) Restrictions

The most likely reason is that your user account does not have the "Execute" permission for that specific scan.

• Scoped Roles: If your role is scoped to only manage certain Agent Tags or Target Tags, and the scan includes assets outside of your scope, you will be "Forbidden" from running it.
• Permission Level: Your role may be set to "Read-Only" or "Analyst," which enables you to view scan definitions and results but prevents you from initiating new jobs.

2. Scan State (Already Running)

Spirion typically prevents you from launching a new instance of a scan if one is already in progress.

• Active Job: Check the Jobs or Recent Activity page. If the scan is currently in a "Starting," "Running," or "Stopping" state, the "Run Scan Now" option is disabled to prevent overlapping work and resource conflicts.
• Queued Work: If the scan has been triggered but is waiting for an Agent to become available, it is considered "Active" and cannot be re-run until the current job completes.

3. Invalid or Incomplete Configuration

If the scan definition is missing critical components, the console will not allow it to run.

• No Agents Assigned: If the scan definition has no Agents (or Agent tags) assigned to it, there is no "worker" to perform the task.
• No Targets Assigned: Similarly, if no data sources (Targets) are selected, the scan has no scope to search.
• Disabled Definition: Ensure the scan definition itself is "Enabled." While you can sometimes run disabled scans manually, some global policies may prevent execution of disabled definitions.

4. Target Authentication Issues

• Expired Tokens: For cloud targets (M365, Google Drive), if the OAuth token has completely expired or the connection is in a "Failed" state, the console may disable the run option until the connection is repaired.

5. Platform Licensing

• License Expiration: If your Spirion license has expired or you have exceeded your licensed quota (e.g., scanning more endpoints than licensed), the ability to initiate new scans may be globally disabled.

Troubleshooting

Use the following high-level steps to troubleshoot this issue:

1. Check Job History: Verify that there isn't already a "Running" instance of the scan.
2. Verify Permissions: Ask an administrator to confirm your role has "Execute" permissions for that scan and its associated tags.
3. Edit the Scan: Open the scan definition and ensure that at least one Agent and one Target are correctly assigned.
4. Check Agent Health: Ensure the Agents assigned to the scan are "Online." If all assigned Agents are offline, the console may prevent the scan from starting.