# Pipeline Scan Settings When configuring [pipeline scans](https://docs.ox.security/scan-and-analyze-with-ox/scanning/scanning-ci-cd-pipelines), you need to define how the scan behaves. You can configure which branches trigger scans, whether to respond to push or pull request events, and how to handle timeouts or scan failures. For example, you might choose to react only to pull requests, which typically represent changes intended for merging into protected branches. OX Security recommends starting with the default configuration and adjusting it based on your workflow needs.


Setting	Description	Recommendation
Timeout	Maximum time a pipeline scan is allowed to run. If exceeded, the scan is terminated. Helps prevent stuck or long-running jobs.	Use default at first. Tune based on observed performance.
Behavior on Error/Timeout	Defines whether the pipeline should be blocked if the scan fails or times out. Failure may not indicate an issue, could be a timeout or data fetch problem.	Start with non-blocking (alert). Move to blocking once pipelines are stable.
Scan Performance Mode	Controls the depth of repository analysis performed during the pipeline scan, as follows: - Detailed scan: Runs the scan with dependency graph generation and also collects Git repository information (Git history and related metadata from the `.git` folder during clone). This mode enables additional context such as information derived from commit history (for example, author-related metadata) and other details based on Git history. - Regular scan: Runs the scan with dependency graph generation. This mode provides dependency-graph-based context, but does not collect Git history information. - Fast scan: Runs the scan without generating the dependency graph.	Available only using feature flag. Use only if needed and enabled for your account. Start with Regular. Use Fast when you need shorter scan times and can work without dependency graph context. The time saved depends on how long dependency graph generation takes for your repositories. Use Detailed when you need Git-history-based context. It can be around 2x slower than Regular depending on the repository.