Analysis timeout in Sema pull request scanner

Direct answer

The available information does not establish a consistent rule for any of the three behaviors. Treat a timed-out Sema pull request scan as incomplete: do not assume partial findings are returned, do not assume policy checks pass or fail uniformly, and do not assume finding deduplication is uniform across stacked pull requests in the same workspace.

Likely explanation versus confirmed facts

Likely explanation (unverified)

• The scanner returns a timeout status instead of partial findings when a per-scan deadline or resource limit is exceeded before results are finalized.
• Diff size, file count, and repository latency are the likely triggers; exact thresholds are not documented in the available material.
• When a timeout occurs, policy checks are likely skipped or marked incomplete according to the workspace enforcement mode, which may be fail-open or fail-closed.
• Deduplication of findings across stacked pull requests is not described consistently and may depend on workspace configuration.

Confirmed facts

• No Sema-specific timeout values, APIs, error codes, or SLA metrics are available in the research brief.
• Behavior may vary by workspace configuration.
• Current verification is required before relying on any of the above.

Steps for this case

1. Inspect Sema workspace integration settings and scanner logs to identify the timeout threshold and the status returned for timed-out PR scans.
2. Trigger a controlled scan with an oversized diff or delayed repository response and observe whether the scanner returns partial findings or a timeout error.
3. Compare duplicate findings across stacked pull requests in the same workspace to determine whether deduplication is applied consistently.
4. Review current Sema documentation or contact support for the authoritative timeout and deduplication policy.

Missing diagnostic detail

What is your workspace's policy enforcement mode for timed-out scans: fail-open (allow the PR) or fail-closed (block the PR)? This detail changes the recommendation because it determines whether a timed-out scan blocks merge or proceeds without complete findings.

Note: This is a conservative draft for human review because the research requires current verification and no authoritative Sema documentation was consulted.