Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: timeout error #601

Closed
wants to merge 3 commits into from
Closed

fix: timeout error #601

wants to merge 3 commits into from

Conversation

paihu
Copy link

@paihu paihu commented Jan 1, 2024

The default timeout of 3 seconds for the Lambda function is too short. I propose we change it to 15 minutes.

@paihu paihu changed the title fix timeout error fix: timeout error Jan 1, 2024
@nabe1653
Copy link

nabe1653 commented Mar 25, 2024

I faced timeout error too in some of my environments ... those enviroment uses same stacks and region but only some envs failed due to timeout error.
I tried to run sometimes and try with --method=prepare-change-set option but not resolved ... so I changed npm_package js code as same as this MR:

            handler: 'remote-outputs.on_event',
+           timeout: aws_cdk_lib_1.Duration.minutes(3),
/*  ... */
            handler: 'remote-parameters.on_event',
+           timeout: aws_cdk_lib_1.Duration.minutes(3),
        });      

I feel 15min is too long but this worked. (I checked lambda log after success, it takes 3.19sec for the env)
I wish merge this or add some args/env-value to choose Duration.

@tochny
Copy link

tochny commented Apr 4, 2024

Facing the same timeout error too but I think 1 to 3 mins would be enough

@pahud
Copy link
Owner

pahud commented Jul 18, 2024

Not sure if we should expose that to the construct props but let's make it 3min timeout for now.

@pahud
Copy link
Owner

pahud commented Jul 18, 2024

close in favor of #604

@pahud pahud closed this Jul 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants