# Your SQS consumer can hang forever by default

DevFeed: [Your SQS consumer can hang forever by default](<https://devfeed.tech/articles/your-sqs-consumer-can-hang-forever-by-default-17823.md>)

Original publisher: [Read original article](<https://encore.dev/blog/message-queue-hangs>)

Author: Ivan Cernja

Published: 2026-07-28T00:00:00Z

Content type: article

Language: en

Sources: [Encore Updates](<https://devfeed.tech/sources/encore-updates.md>)

Topics: [Amazon Simple Queue Service (SQS)](<https://devfeed.tech/topics/amazon-simple-queue-service-sqs.md>), [SDK](<https://devfeed.tech/topics/sdk.md>), [Rust](<https://devfeed.tech/topics/rust.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [health-check](<https://devfeed.tech/tags/health-check.md>), [queue](<https://devfeed.tech/tags/queue.md>), [retry](<https://devfeed.tech/tags/retry.md>), [rust](<https://devfeed.tech/tags/rust.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [sqs](<https://devfeed.tech/tags/sqs.md>), [tcp](<https://devfeed.tech/tags/tcp.md>), [timeout](<https://devfeed.tech/tags/timeout.md>)

## AI overview

The article explains that the AWS Rust SDK has no request timeout by default. A failed or silently dropped connection can leave an SQS receive waiting indefinitely, stopping a sequential consumer loop while the process and health check still appear healthy. It describes fixing the issue with a per-attempt timeout.

## Source excerpt

The AWS Rust SDK ships no request timeout by default, so one SQS receive on a dead connection can hang a whole consumer with nothing in the logs.