Netlify incorrectly tampering requests from scheduled functions?

I am testing a scheduled function that simply writes a file to an S3 bucket. I am using the latest version of the official AWS SDK.

When I invoke the function locally with netlify dev and netlify functions:invoke test, it works perfectly.

However, in production, I always get the following error message:

May 16, 09:40:04 PM: INIT_START Runtime Version: nodejs:20.v22	Runtime Version ARN: arn:aws:lambda:us-east-2::runtime:b41f958332022b46328145bcd27dce02539c950ccbf6fde05884f8106362b755
May 16, 09:42:02 PM: 2c0cb6d2 INFO   Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
    at ClientRequest.setHeader (node:_http_outgoing:659:11)
    at addHeaders (file:///var/task/___netlify-bootstrap.mjs:1890:13)
    at patchedRequest (file:///var/task/___netlify-bootstrap.mjs:1916:7)
    at /var/runtime/node_modules/@aws-sdk/node_modules/@smithy/node-http-handler/dist-cjs/index.js:233:19
    at new Promise (<anonymous>)
    at _NodeHttpHandler.handle (/var/runtime/node_modules/@aws-sdk/node_modules/@smithy/node-http-handler/dist-cjs/index.js:189:12)
    at async /var/runtime/node_modules/@aws-sdk/middleware-flexible-checksums/dist-cjs/index.js:257:18
    at async /var/runtime/node_modules/@aws-sdk/node_modules/@smithy/middleware-serde/dist-cjs/index.js:33:24 {
  '$metadata': { attempts: 1, totalRetryDelay: 0 }
May 16, 09:42:02 PM: 2c0cb6d2 Duration: 158.21 ms	Memory Usage: 26 MB

The relevant part of my package.json:

  "dependencies": {
    "@aws-sdk/client-s3": "^3.577.0"

Version 3.577 is the latest. I have tried both the latest version of the AWS SDK and an earlier version.

The relevant part of my netlify.toml:

  schedule = "* */4 * * *"

I have tried both Node.js version 18.x and 20.x in the Netlify web UI.

The code of my function:

import { PutObjectCommand, S3Client } from '@aws-sdk/client-s3'

export default async () => {

  const s3 = new S3Client({
    region: MY_AWS_REGION,
    credentials: {
      accessKeyId: MY_AWS_ACCESS_KEY_ID,
      secretAccessKey: MY_AWS_SECRET_ACCESS_KEY,

  const command = new PutObjectCommand({
    Body: 'Hey!',
    Bucket: 'boletinde',
    Key: '/test.txt',

  let response

  try {
    response = await s3.send(command)
  } catch (error) {

The environment variables with my AWS credentials are correctly configured. My AWS region is eu-south-2.

My site is deployed at ( It builds successfully and the function is triggered as per the schedule.

I know that scheduled functions are in beta.

Does anyone know what could be going wrong?

From what you’ve provided I only know what you likely already know.
Something in the function is trying to send a response after already having sent one.

However I don’t see obvious evidence of that in the sample code of your function.

Thanks for your response, @nathanmartin!

Actually, there would be no issue with sending multiple s3.send() requests successively. For example, to upload multiple files to S3 from the same function.

To me, this doesn’t seem to be an error with the AWS SDK, which is a mature library maintained by Amazon. Nor does it seem to be an issue with my code, as it’s simple and works in my local environment. I might be wrong, but I would say it’s a problem with Netlify’s runtime environment.

The call stack in the error trace shows how the execution flow is passed to @aws-sdk, but then it is intercepted by the Netlify runtime environment, which seems to patch the request (patchedRequest) and add new headers (addHeaders), all from /var/task/___netlify-bootstrap.mjs:

    at addHeaders (file:///var/task/___netlify-bootstrap.mjs:1890:13)
    at patchedRequest (file:///var/task/___netlify-bootstrap.mjs:1916:7)

And that’s where the execution fails and stops.

The sending of the request to S3 is entirely managed by the AWS SDK, which first sets the request headers and immediately sends its body. It seems that something is then trying to send additional headers. There is nothing in my code—nor can there be—that causes this interference.

That’s why I think there is some kind of issue in Netlify’s runtime environment.

@JaimeObregon I was only addressing your open ended question, as from my experience ERR_HTTP_HEADERS_SENT means precisely as it says:

Cannot set headers after they are sent to the client

You’ll see as much if you google around.

But it sounds like you’re speaking from a position of authority so you likely know more than I do.

Note: I don’t work for Netlify.