---
title: "Comment by Andrew on \"My Idle Background Worker Was the Most Expensive Thing I Owned\" | Hashnode"
description: "Eager mode is useful, but Cloud Run's request timeout is now the only bound your inline tasks have. A hung SMTP call that used to die at task_time_limit now sit"
url: "https://hashnode.com/posts/my-idle-background-worker-was-the-most-expensive-thing-i-owned/6a8e33d71011e317aa404c6d/comment/6a8e4894073adfd2569bdb4d"
---

[Discussion](https://hashnode.com/posts/my-idle-background-worker-was-the-most-expensive-thing-i-owned/6a8e33d71011e317aa404c6d)

Comment [My Idle Background Worker Was the Most Expensive Thing I Owned](https://hashnode.com/posts/my-idle-background-worker-was-the-most-expensive-thing-i-owned/6a8e33d71011e317aa404c6d)

[Andrew](https://hashnode.com/@rizzdev)

[Aug 26](https://hashnode.com/posts/my-idle-background-worker-was-the-most-expensive-thing-i-owned/6a8e33d71011e317aa404c6d/comment/6a8e4894073adfd2569bdb4d)

Eager mode is useful, but Cloud Run's request timeout is now the only bound your inline tasks have. A hung SMTP call that used to die at task\_time\_limit now sits on signup until the service timeout fires. Tune that number before a slow provider turns the hang into a 504 on signup.

[Ashish Kr Jha](https://hashnode.com/@Ashish14411)

[Aug 29](https://hashnode.com/posts/my-idle-background-worker-was-the-most-expensive-thing-i-owned/6a8e33d71011e317aa404c6d/comment/6a8e4894073adfd2569bdb4d#reply-6a929f0739c3135e39ff0a85)

Good catch. Once the task moves inline, the request timeout becomes part of the same failure budget. Bounded it at 5s per attempt and 12s total across attempts and backoff. The post also understates the normal case, since signup sends two emails sequentially, so that needs a correction too.
