---
title: "Explain a deploy check with too little service traffic | Proofline Help"
description: "Read the deployment’s Checks section when a quiet service or a brief sample leaves too little traffic for a conclusion. Check the request signal alongside the outcome."
url: https://proofline.sh/help/deploy-traffic-floor/
---

[Help center](/help/)

# Explain a deploy check with too little service traffic

Read the deployment’s Checks section when a quiet service or a brief sample leaves too little traffic for a conclusion. Check the request signal alongside the outcome.

## Interpret traffic floors and request evidence

A window in which a service served almost nothing says little about its signals. To keep such a window from reading **No regression**, an administrator can edit the signal that sums or counts a service's requests, select **Counts the service's requests** and set its **Traffic floor (requests per window)**, 100 unless changed. A check whose window, or the hour or day before it compares with, counted fewer requests is **Incomplete**, and a signal of that service that regressed still reads **Regressed**. On the deploy's page, an administrator sees **Too few requests to judge a service's signals** with no step. It names each request signal whose window counted fewer requests than its floor in the newest check that recorded the gap, with that count and the floor. The floor covers the signals that name the same service where it runs, or, for a request count that names no service, the other signals that name none. A service takes one such signal, and a service without one is checked as before.

When a request signal regressed and the check read its service's request log, the routes follow that check under **Failing routes on** and the service's name. **Window** and **Revisions** say which minutes the check read and which of the service's revisions of the deployed commit served them. Each row is a route's method and path with its **Requests**, its **Server errors** and the requests Cloud Run ended **At timeout**; a request ended at the timeout counts as a server error too. The check lists at most five routes that answered a server error: those that ran to the timeout first, then the rest by server errors. A path shows `{id}` in place of numbers and IDs. When the read found no failing route, the section keeps **Window** and **Revisions** and says "No route answered with a server error." When the read failed, the log was too large for one read, or the routes were withheld to protect sensitive values, the check shows no routes. If Google Cloud refused the read, an administrator sees **Request log read refused** with **Check Google Cloud access**. The routes never change a check's result.

## Related guides

-   [Read a deploy's verification](/help/read-deploy-verification/)
-   [Turn on the production loop for AWS](/help/aws-production-loop/)
