I would recommend enabling execution logs on API Gateway and check the logs there for any failures. I would guess that it has something to do with the format of the response being sent from the Lambda function.
This problem is solved by increasing quota for concurrency.
Return a custom header from lambda authorizer in API-gateway (HTTP api)asked 4 months ago
Lambda (private subnet) <- ingress request< - gatewayAccepted Answerasked 8 months ago
Api Gateway with Lambda Integration Failureasked 9 months ago
Client API Throttling in API GatewayAccepted Answerasked 2 years ago
API Gateway Timeouts from Lambdaasked 4 years ago
Deploy Lambda Function and API Gateway RESTasked 7 months ago
API Gateway, Lambda and CORSasked a year ago
Lambda response compression to API Gateway and clientasked 8 months ago
Binary uploads to API Gateway Proxy with Lambda IntegrationAccepted Answerasked 6 years ago
Lambda Authorizer with API Key enabled on API Gatewayasked 6 months ago