# Unexpected SQS Messages

**URL:** <https://forum.serverless.com/t/unexpected-sqs-messages/13202>\
**Category:** Serverless Framework\
**Tags:** aws\
**Created:** [November 24, 2020, 6:38pm UTC](https://forum.serverless.com/t/unexpected-sqs-messages/13202 "2020-11-24T18:38:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![davidfells](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/davidfells/32/4771_2.png) [@davidfells](https://forum.serverless.com/u/davidfells)\
**Post date:** [November 24, 2020, 6:38pm UTC](https://forum.serverless.com/t/unexpected-sqs-messages/13202/1 "2020-11-24T18:38:12Z")

</div>

First off, my serverless.yml: [https://gist.github.com/davidfells/15169c9afda25b02de4bb386d77b814a](https://gist.github.com/davidfells/15169c9afda25b02de4bb386d77b814a)

In CloudWatch, all of my SQS queues show they are receiving ~15 empty receives **every few seconds**. As you can imagine this is racking up usage pretty rapidly. I have no idea where the messages are coming from. No other applications touch this stack.

I’ve confirmed that all the Lambdas have the right triggers and that they aren’t running excessively. In fact, my scheduled Lambda doesn’t run at all unless I manually invoke it. Dead letter queues aren’t creating either, which is odd.

Latest version of serverless and all plugins, no errors in my output, the only warnings that appear are expected and related to the iam policies plugin.