---
title: "Comment by Kartik N V J K on \"Retries Are a Latency Budget, Not a Boolean\" | Hashnode"
description: "Your nine-attempt math should be plain in the logs. \"Number of attempts, where available\" gets fuzzy when the SDK retries inside what the job runner sees as one"
url: "https://hashnode.com/posts/retries-are-a-latency-budget-not-a-boolean/6ae1e4f45706d7cfc1b70b59/comment/6ae34fab289414ae0e7fef21"
---

[Discussion](https://hashnode.com/posts/retries-are-a-latency-budget-not-a-boolean/6ae1e4f45706d7cfc1b70b59)

Comment [Retries Are a Latency Budget, Not a Boolean](https://hashnode.com/posts/retries-are-a-latency-budget-not-a-boolean/6ae1e4f45706d7cfc1b70b59)

[Kartik N V J K](https://hashnode.com/@kartik-nvj)

[Oct 29](https://hashnode.com/posts/retries-are-a-latency-budget-not-a-boolean/6ae1e4f45706d7cfc1b70b59/comment/6ae34fab289414ae0e7fef21)

Your nine-attempt math should be plain in the logs. "Number of attempts, where available" gets fuzzy when the SDK retries inside what the job runner sees as one try, so I log the count at each layer separately. Then a slow request tells me which layer spent the time.
