Closed hannahle closed 1 year ago
Preview app for this PR's source branch: https://hannah-timeout-bump.d1w6d75be7tofa.amplifyapp.com/
@hannahhanle I think this will solve any time-out issue, as of right now AWS-Lambda has a hard-coded timeout after 5 minutes. The page refreshes 60 times (every 5 seconds) and after 5 minutes if an output is not generated it is assumed that the lambda-function has self-terminated. If you're increasing refreshes to 10 minutes, the lambda timeout has to be adjusted as well.
@hannahhanle I think this will solve any time-out issue, as of right now AWS-Lambda has a hard-coded timeout after 5 minutes. The page refreshes 60 times (every 5 seconds) and after 5 minutes if an output is not generated it is assumed that the lambda-function has self-terminated. If you're increasing refreshes to 10 minutes, the lambda timeout has to be adjusted as well.
Yes, this is what I did. I already adjusted the lambda timeout as well!
Summary of changes
The number of requests before a timeout is bumped from 60 to 120.
Checklist
Manual testing
Here's an example of a sequence that used to fail on a 60-request timeout limit:
After increasing the request limit, an error report was returned as expected here: https://s3.amazonaws.com/openvirome.com/betaflax_sativa.html
In addition to the change made here, the timeout for the PalmID Lambda API function was also bumped from 5 minutes to 10 minutes.