K6- Studio -- InvalidEventFormat in Content

Hi ,
I using K6 Studio , I am able to record and when validating test script I see in Content of the POST URL .Anyone faced this kind of issue ? Please suggest how to overcome this error.
“acc”: 0,
“efi”: {
“InvalidEventFormat”: “all”

Hi and welcome!

I wanted to confirm if that specific endpoint is something you are trying to test directly or is it a third party host that happens to be included in the application you are testing ? :thinking:

If it’s the latter, the advised solution would be to remove third-parties hosts from your script, you can select/deselect the hosts in the top-right of the Generator:

We are working to make it easier to not enable third-party hosts in the future as easily since they are usually not the thing the user is trying to test and sometimes have special syntax, I hope this helps!

Hi ,
This is not third-party call , this API call is bypassing SSO and authenticating the user to SignIn the application. I correlated all the values needed to SignIn but when validating the script In SignIn group I am not able to get 100% Success nor I can see logs to debug the issue in K6 Studio.I am struck at Sign In group .

Any suggestion how to proceed will be helpful .

When trying to correlate dynamic value , I see like below

For First Match , I see the value is getting captured , please correct if I am wrong . I understand Most recent match option replaces values in next request of API calls ,so it is good if most recent match can capture values correctly between left boundary and right boundary

The difference between First match and Most recent match is regarding extraction, first match is going to extract the first value found and use that in all subsequent matched requests.

Most recent match is going to extract the value every time it finds it meaning that you are always going to use the latest extracted one. (This is useful if you don’t want to add more rules to extract the same pattern multiple time)

Regarding the issue per se, in the response content we see that it’s complaining regarding the invalid format the endpoint, you can check what it’s being sent in the payload section in the Request panel, it’s not a specific log that Studio should be reporting but an error that should be documented by the endpoint you are using. Since the content of the response is not explaining much I would probably advise to check the documentation of the service and double check with the payload to see what’s actually wrong in the format between the two :thinking:

I tried to filter API calls and work on correlation .
I still see my success rate for group enter passwordClick signIn is 90% and enter searchterm is 50%

The workflow from here is to check the failing requests in the validation → create rules to fix the failing requests → validate again.

Currently the checks are not reported to the specific failing request so that you have to check yourself in the validation list but we are working to make it simpler!