Apparently the error does not come from HTTP 422, it comes from plan permanent identifier vs plan id not being found in the cached plan data in the client. So something is wrong with how the client uses ids in case the permanent identifier is filled?
https://eu-central-1.console.aws.amazon.com/cloudwatch/home?region=eu-central-1#logsV2:log-groups/log-group/$252Faws$252Flambda$252Fhame-dev-ryhti_client/log-events/2024$252F06$252F04$252F$255B$2524LATEST$255D210be8cb22794482b89549cac67c9ebe
Apparently the error does not come from HTTP 422, it comes from plan permanent identifier vs plan id not being found in the cached plan data in the client. So something is wrong with how the client uses ids in case the permanent identifier is filled?