That is odd behaviour. I'd strongly encourage you to raise a support ticket to investigate that particular issue.
Otherwise: I don't think your strategy of using Lambda Layers is quite right. Yes, it might work but storing different data in each Layer is probably a bad pattern to use. My guess is that you're doing it so that the Lambda function doesn't have to load anything externally at startup but it still seems a little wrong.
Please reach out to your local AWS Solutions Architect to talk about your requirements and the best way to achieve that. Or: Ask a question here on re:Post with what you're trying to achieve.
Deploy lambdas in parallel with CodeBuildAccepted Answerasked a year ago
auto update AWS Lambda Application with lambda referencing layerAccepted Answerasked a year ago
new Lambda Function URL with TerraformAccepted Answerasked 8 months ago
Using Terraform with AWS SSO accountsasked 4 months ago
AWS SAM Layer makes too many versionsasked 9 months ago
How to ensure using the latest lambda layer version when deploying with CloudFormation and SAM?Accepted Answerasked 6 months ago
Deploy Lambda Function and API Gateway using Terraformasked 10 months ago
Racing condition of IAM role creation and AWS resourcesAccepted Answerasked 4 years ago
Issue creating Lambda function layer versions in parallel processasked 8 months ago
Security implications of SourceArn (as in AWS::Lambda::Permission)asked 3 years ago