This is likely fixed now so you may want to try again. There was an issue on a new serverless-v2 API that has now been resolved. (Details at this link.)
1 Like
This is likely fixed now so you may want to try again. There was an issue on a new serverless-v2 API that has now been resolved. (Details at this link.)