title: Lambda does not send message to SQS destination if invoked by an SQS source
body: <p>I have the following set up:</p>
  <p><a href="https://i.stack.imgur.com/l0aUY.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/l0aUY.png" alt="SQS#1 -&gt; Lambda -&gt; SQS#2" /></a></p>
  <p>I have a simple return in my Lambda function right now:</p>
  <pre><code>async function handler(event) {
    return 'success';
  }
  </code></pre>
  <p>If I invoke the lambda from the aws-cli using:</p>
  <pre><code>aws lambda invoke --function-name tt-yt-automation-production-1b2b-tiktok-download --invocation-type Event --cli-binary-format raw-in-base64-out /dev/null
  </code></pre>
  <p>It will return the message to the destination SQS (<code>SQS#2</code>), which will trigger another Lambda.</p>
  <p>However, if <code>SQS#1</code> has a message and invokes the Lambda, it does not send a message to <code>SQS#2</code> and invokes the next Lambda in line.</p>
  <p>My suspicion is that an SQS invocation doesn't count as an <code>asynchronous invocation</code> and won't send a message to <code>SQS#2</code>.</p>
  <p>Is there a configuration I'm missing?</p>