Hey @RinKimLaw I tried making a repro (albeit with just the graphql function) and couldn't reproduce 8-10 minute looping builds. One thing I'm wondering: is the @vercel/redwood package a Vercel runtime? Basically, where did you see docs to use that package as the runtime, or did Vercel support tip you off to that?

I'm wondering if that's the problem. I feel like maybe you should actually end up using the Node.js runtime via @vercel/node?

Hi @jtoar, I'm running into the same issue here trying to extend my function timeouts.

The selection of the runtime is referenced in the docs here. It seems this was suggested by vercel support to a user in this community post.

As it stands, the default deploy that runs the @redwood/vercel builder is not picking up the maxDuration property being exported from my functions so function executions are limited to 15 seconds even on the Pro plan.

It appears that targeting the root graphql file only will allow you to customize options for the server file but not the nested functions. Building will succeed with this configuration

{
  "functions": {
    "api/src/functions/*.*": {
      "maxDuration": 20,
      "runtime": "@vercel/[email protected]"
    }
}

Attempting to set options for a nested function will result in recursive builds

{
  "functions": {
    "api/src/functions/*.*": {
      "maxDuration": 20,
      "runtime": "@vercel/[email protected]"
    },
    "api/src/functions/nestedFunction/*.*": {
      "maxDuration": 300,
      "runtime": "@vercel/[email protected]"
    }
  }
}

I have verified this both with the local vercel build command and in the platform builds.

This restricts customization and pretty much rules out vercel as viable platform for all but the most simple apps built with redwood.

For context I am also running "@redwoodjs/core": "6.6.0"

I think there's a way to configure the vercel.json for redwoodjs that's not completely/accurately documented anywhere because with the default settings (No vercel.json), the project deploys within 1m30s. Also, all the config in my vercel.json is ignored, the memory size is always the default 1024MB.

I believe that https://community.redwoodjs.com/t/increase-timeout-duration-of-api-in-vercel/5446/3 address this issue with some docs to set the timeout on Vercel.

But I may be wrong?

Just to clarify - this issue related to the length of the build time (not the timeout of the function) -- because Vercel is building the redwoodJS app multiple times (once per api/function)?

@dthyresson That documentation only works for the base graphql function. If you try to specify a different timeout or memory settings for the serverless functions in sub-directories, it will build recursively, not just once per function

I wonder if there's any update on this? I previously tried to post this as an issue on Vercel's github but couldn't get through. For now it's fine deploying Redwood to vercel with default settings for me, but it's a pretty major issue that neither the function size nor the function timeout can be adjusted using vercel.json.

Hi @RinKimLaw - I am trying to remember the details but does this https://redwoodjs.com/docs/deploy/vercel#verceljson-configuration help?

I imagine that one might have to specify a function (not the GraphQL function listed)..

I’d this does not help, could you share an example that does not work as expected?

@dthyresson No that config didn't work for me. It eventually deploys after recursively building everything, but neither of the function parameters are honoured (Memory or timeout).

Opened an issue on Vercel's side https://github.com/orgs/vercel/discussions/6526

@RinKimLaw We will likely have to create a small reproducible case for Vercel to try. Do you have a public repo of a project we can share or could you post the Vercel config you are using to make sure we’re doing the same. Thanks.

@dthyresson I can setup a public repo tomorrow to demo the issue.

@dthyresson I can setup a public repo tomorrow to demo the issue.

Thank you so much! This will really help as I can share with Vercel, too.

Hi, just on my personal account -
Here is the test repo - https://github.com/DrakenKor/vercel-redwood-tester
Vercel.json values:

{
  "buildCommand": "yarn rw build",
  "functions": {
    "api/src/functions/tester1/tester1.*": {
      "memory": 256,
      "runtime": "@vercel/[email protected]",
      "maxDuration": 20
    },
    "api/src/functions/graphql.*": {
      "memory": 512,
      "runtime":"@vercel/[email protected]",
      "maxDuration": 30
    }
  }
}

Values are not honoured for the tester1 function. The build is also recursive and builds twice, once for each function.

Vercel deploy settings:

We are still experiencing this issue months later, to great frustration. Same issue as @DrakenKor

Hi @bencohen4 have you spoken with to Vercel? Did they give any insight?

I’ll connect with them to understand how they build and try to reproduce.

I haven’t deployed to Vercel recently. Do they have a local build process like Netlify does that builds locally like they would when deployed?

Hi @bencohen4 have you spoken with to Vercel? Did they give any insight?

I’ll connect with them to understand how they build and try to reproduce.

I haven’t deployed to Vercel recently. Do they have a local build process like Netlify does that builds locally like they would when deployed?

Hi @dthyresson I did open up a support ticket with Vercel, they did offer some suggestions but those didn't end up working unfortunately. The case was dropped around the end of January.

They do have a local vercel build command.

CC'ing @will-govwell for visibility

Vercel got back to me and I’ll try my own deploy to reproduce. For reference: theypointed me to the redwood build “adapter” https://github.com/vercel/vercel/blob/main/packages/redwood/src/index.ts

Also could people @bencohen4 and others share the Vercel config they use?

Does it specify the runtime? One thing we want to try is if the runtime setting is removed from each function config.

The hypothesis to test is that this build handler is called when a Redwood app builds. By setting that runtime in effect one says build the function with this very same build handler again .. and again per function.

If no runtime is defined then we think the config should just be config settings and not trigger additional builds.

if you could try that please let me knew of see any difference in build time and logs.

@dthyresson here is my vercel.json config:

{
  "functions": {
    "api/src/functions/*": {
      "maxDuration": 60,
      "runtime": "@vercel/[email protected]"
    }
  }
}

Removing the runtime failed the deployment with the error "Error: The pattern "api/src/functions/*" defined in functionsdoesn't match any Serverless Functions inside theapi directory."

Removing the runtime

Thanks for trying- could you try it you specify a non glob path? And specify the function file directly?

Will give it a go and let you know! Thanks @dthyresson

Will give it a go and let you know! Thanks @dthyresson

Btw a local “vc build” using the Vercel cli they said should build the same way and should reproduce

@dthyresson using this vercel.json:

{
  "functions": {
    "api/src/functions/graphql.ts": {
      "maxDuration": 60,
      "runtime": "@vercel/[email protected]"
    }
  }
}

Yielded a build that took 2x as long as usual - because the steps were indeed duplicated - and the resulting Vercel deployment is still maxing out at 15 seconds, not 60 like my vercel.json implies

@dthyresson using this vercel.json:

{
  "functions": {
    "api/src/functions/graphql.ts": {
      "maxDuration": 60,
    }
  }
}

Sorry. I may not have been clear ^^* we wanted to try without the runtime value.

@dthyresson using this vercel.json:

{

"functions": {

"api/src/functions/graphql.ts": {

  "maxDuration": 60,

}

}

}

Sorry. I may not have been clear ^^* we wanted to try without the runtime value.

@dthyresson I tried this earlier. Sorry for not being clear - Removing the runtime failed the deployment with the error "Error: The pattern "api/src/functions/*" defined in functionsdoesn't match any Serverless Functions inside theapi directory."

Hello @bencohen4 and @DrakenKor happy to finally give you both some promising news.

Having spoken to Vercel, they have opened an internal issue to fix this.

They have suggested to support configuring the function in the function code itself rather than the vercel.jsonl For example:

import type { APIGatewayEvent, Context } from 'aws-lambda'

import { logger } from 'src/lib/logger'

export const config = {
  maxDuration: 30,
}

export const handler = async (event: APIGatewayEvent, _context: Context) => {
  logger.info(`${event.httpMethod} ${event.path}: tester1 function`)

  return {
    statusCode: 200,
    headers: {
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({
      data: 'tester1 function',
    }),
  }
}

I'll update here when I get word on a release fix.

And just to let know, yes -- because of the way Vercel's Redwood builder worked, the entire app could recursively build on build n time per function config.

This behavior can be seen in logs of simply via a vercel build in your local project.

Hope to have good new soon.

BTW

I like this in function config as it:

• is nice for functions used with Inngest to see and match and timeout durations
• makes it easier if use custom templates and add that section
• could be a pattern to follow for other jobs when redwood has a job runner.

Thank you @dthyresson!!
Just to confirm - the export const config = {} suggestion is not something that would be available to us without an update from Redwood, right? As we are blocked by the createGraphQLHandler function's setup. And also Vercel does not support this yet either.

I agree that defining the config in the function is likely much easier than defining it in json files - less room for errors

suggestion is not something that would be available to us without an update from Redwood, right?

Actually, it's an update necessary to the Vercel builder that handles the Redwood framework here: https://github.com/vercel/vercel/blob/main/packages/redwood/package.json

suggestion is not something that would be available to us without an update from Redwood, right?

Actually, it's an update necessary to the Vercel builder that handles the Redwood framework here: https://github.com/vercel/vercel/blob/main/packages/redwood/package.json

Got it. So we are now waiting on Vercel to make a code change to https://github.com/vercel/vercel/blob/main/packages/redwood/package.json then?

we are now waiting

Once they tell me it's fixed and they released, I'll let you know here -- after I confirm and also update the RedwoodJS docs.

we are now waiting

Once they tell me it's fixed and they released, I'll let you know here -- after I confirm and also update the RedwoodJS docs.

thanks!!

Thanks, this'll mean I can start using Redwood on Vercel again.

Have tested fix shown here vercel/vercel#11776 and looking good. Just will have to wait for that to get approved, released and published.

via

export const config = {
  maxDuration: 30,
  memory: 512,
}
``` in the function etc.

Have tested fix shown here vercel/vercel#11776 and looking good. Just will have to wait for that to get approved, released and published.

via

export const config = {

  maxDuration: 30,

  memory: 512,

}

``` in the function etc.

Omg @dthyresson thank you!!! Can't wait!