---
title: "Consecutive HTTP"
description: "Learn more about Consecutive HTTP issues and how to diagnose and fix them."
url: https://docs.sentry.io/product/issues/issue-details/performance-issues/consecutive-http/
---

# Consecutive HTTP

Consecutive HTTP issues are created when at least 2000ms of time can be saved by parallelizing a minimum of 3 consecutive HTTP calls occurring sequentially.

Filter HTTP client performance issues with `issue.category:http_client` in **Issues** and **Dashboards**.

## [Detection Criteria](https://docs.sentry.io/product/issues/issue-details/performance-issues/consecutive-http.md#detection-criteria)

This issue is only available for backend and mobile SDKs.

The Consecutive HTTP detector looks for a set of sequential, non-overlapping HTTP spans. It intentionally ignores unrelated, non-HTTP operations that occur between HTTP spans.

Once this sequence is found, the following must hold true for each HTTP span:

* The HTTP method must be a GET, POST, DELETE, PUT, or PATCH
* The HTTP URL must not contain `\_next/static/` , `\_next/data/` , or `googleapis.com`

Once these spans are found, the following must also hold true:

* Minimum time saved from parallelization must exceed `2000ms`
* The duration of each HTTP span must exceed a threshold of `500ms`.
* The time between each HTTP span must not exceed a threshold of `500ms`.
* The number of sequential HTTP spans must exceed a threshold of `3`.

If Sentry doesn't detect a Consecutive HTTP issue where you expect one, it's probably because the transaction didn't meet one of the above criteria.

You can configure detector thresholds for Consecutive HTTP issues in **Project Settings > Performance**.

## [Span Evidence](https://docs.sentry.io/product/issues/issue-details/performance-issues/consecutive-http.md#span-evidence)

You can find additional information about your Consecutive HTTP issue by looking at two main aspects in the "Span Evidence" section:

* **Transaction name**
* **Offending Spans**

You can view the span evidence by going to the **Issues** page in Sentry, selecting your project, selecting the Consecutive HTTP Queries error you want to examine, then scrolling down to the "Span Evidence" section.

## [Fixing Consecutive HTTP Issues](https://docs.sentry.io/product/issues/issue-details/performance-issues/consecutive-http.md#fixing-consecutive-http-issues)

The causes of Consecutive HTTP issues vary, but here are some suggestions to help you resolve them:

* If your HTTP spans are independent, consider parallelizing them so they're no longer sequential.
* If you have control over the backend, consider optimizing your endpoints for this specific use case. You can investigate corresponding backend transactions to help identify potential improvements.