Missing num error while executing state machine

[gaurav-eagleview]

We executed the state machine with the following input: { "lambdaARN": "arn:aws:lambda:us-east-2:356071293939:function:test_lambda", "powerValues": [ 128, 256 ], "num": 2, "payload": {} }

and got the below error in the initializer:

"error": { "Error": "Error", "Cause": "{\"errorType\":\"Error\",\"errorMessage\":\"Missing num or num below 5\",\"trace\":[\"Error: Missing num or num below 5\",\" at validateInput (/var/task/initializer.js:52:15)\",\" at module.exports.handler (/var/task/initializer.js:14:5)\",\" at Runtime.handleOnceNonStreaming (file:///var/runtime/index.mjs:1173:29)\"]}"

What can be the probable cause of it?

[tbruccoleri]

@gaurav-eagleview You'll need to use a number greater than 5, the current value you have is 2.

https://github.com/alexcasalboni/aws-lambda-power-tuning/blob/6272a6b5d8bfee95365899e3b64c243ca00b769f/lambda/initializer.js#L51

[alexcasalboni]

@gaurav-eagleview @tbruccoleri correct :)

As for the error message in the stack trace: "Error: Missing num or num below 5".

I know this might sound like a meaningless error, but the reasoning is that if the number of invocation is too small you will not get statistically relevant results. I'd usually recommend num>=50 to make sure the average invocation time & cost are useful to take an optimal decision.

[gaurav-eagleview]

@alexcasalboni @tbruccoleri : Thanks for the quick support. I understood now. It worked like a charm now :)

[gaurav-eagleview]

Closing this