Build script returned non-zero exit code. Deploy did not succeed with HTTP Error 400

I’m having the same problem with a Remix app.

Site name
omg-dmc
Owner
Office music game
Site ID
0df9e5ae-5121-4e5c-9d0e-b2a7ede011c5

Could I please be excluded from the rollout as well?

Our website is having a same issue.

Site ID: 2d72d9d5-1985-4149-8aa2-97c4b0f9ff4d
Site name: lofaseoul-partner

I want our website to be excluded from problematic update as other people were.
Thank you.

hello @taejung1205 & @dmc1985 :wave:t6: thanks for reaching out! I have escalated your request to our helpdesk. Our team will follow up with you via email shortly.

Cheers,

Sam

1 Like

Hello, can I get similar exemption for my recently delpoyed site? I need to roll-out updates

Which site are you asking about?

Hello!
We have the same issue, can you fix it for our website?

website id = c8c33898-a2a1-4b92-b24c-fe2cc16b6530
deployment id = 6675cce3dd68c8d8dafc23f3

The same error during the functions upload.

9:00:30 PM: Failed to create function on AWS Lambda: invalid parameter for lambda creation: Invalid AWS Lambda parameters used in this request.
9:00:30 PM: Failed to create function on AWS Lambda: invalid parameter for lambda creation: Invalid AWS Lambda parameters used in this request.
9:00:30 PM: Failed to upload file: algolia-sanity-sync
9:00:30 PM: Failed to upload file: contact_form
9:00:30 PM: Section completed: deploying
9:00:30 PM: ​
9:00:30 PM: Error deploying                                               
9:00:30 PM: ────────────────────────────────────────────────────────────────
9:00:30 PM: ​
9:00:30 PM:   Error message
9:00:30 PM:   Deploy did not succeed with HTTP Error 400: [PUT /deploys/{deploy_id}/functions/{name}][400] uploadDeployFunction default  &{Code:400 Message:Failed to create function on AWS Lambda: invalid parameter for lambda creation: Invalid AWS Lambda parameters used in this request.}
9:00:30 PM: ​
9:00:30 PM:   Error location
9:00:30 PM:   At deploy the stage with HTTP status code '400'

@alex3 I’ve excluded you from the feature, you should now be able to successfully deploy

Thanks, but we still see the same error (

I tried all possible AWS_LAMBDA_JS_RUNTIME values, right now it’s deleted and still, it does not deploy.

e.g. deployment id = 66769da4235f9b731fa5c1f3

Please help.

@alex3 sorry about that, I’ve made a change on my end, can you give it another try and let me know if you’re successful?