---
title: "Comment by Ahmet Özel on \"Retry Is a Buffered-World Habit. Streaming Punishes It.\" | Hashnode"
description: "The content-exposed flag should be monotonic across all attempts for the logical request. A fallback must not reset it merely because the new provider has not e"
url: "https://hashnode.com/posts/retry-is-a-buffered-world-habit-streaming-punishes-it/6ad717825c1a30ac03fca697/comment/6ad72f06bb592a040f24c663"
---

[Discussion](https://hashnode.com/posts/retry-is-a-buffered-world-habit-streaming-punishes-it/6ad717825c1a30ac03fca697)

Comment [Retry Is a Buffered-World Habit. Streaming Punishes It.](https://hashnode.com/posts/retry-is-a-buffered-world-habit-streaming-punishes-it/6ad717825c1a30ac03fca697)

[Ahmet Özel](https://hashnode.com/@ahmetozel)

[Oct 20](https://hashnode.com/posts/retry-is-a-buffered-world-habit-streaming-punishes-it/6ad717825c1a30ac03fca697/comment/6ad72f06bb592a040f24c663)

The content-exposed flag should be monotonic across all attempts for the logical request. A fallback must not reset it merely because the new provider has not emitted anything yet; the earlier prefix may already be visible.

I would keep a separate attempt ID under the request ID, with each attempt's exposure state, terminal state and unsettled usage. Then test a disconnect immediately after the gateway writes its first content frame, where delivery to the browser may be uncertain. Treating that uncertainty conservatively prevents the recovery layer from declaring a fresh retry invisible when it cannot actually establish that boundary.
